A publishing queue that recovers after a restart
A controlled queue matters more than raw speed: stopping to verify an uncertain result is safer than creating duplicates or cascading errors.
Every action is a separate job
Publication, recipient, account, time, status and result are stored separately, so one failure does not erase the rest of a campaign.
Verify before retrying
UNKNOWN means the result is uncertain. The app first checks for a published post or moderation entry.
A transparent history
The campaign summary separates published, queued, rejected and failed jobs, with links to inspect results.
Multiax does not guarantee that social platforms will never impose restrictions. Use your own or authorized accounts and follow platform rules.
Frequently asked questions
What happens if the app closes mid-campaign?
After restart, Multiax restores the queue and verifies unfinished jobs.
Can a campaign be stopped safely?
Yes. New jobs stop starting while operations already in progress are allowed to finish.