Scheduled and sent posts
How scheduled posts go out, how to cancel one, what History shows, and what to do when a platform refuses a post.
Scheduled posts
Scheduled lists every post the workspace has queued, soonest first, including posts the Auto-poster has written. m.social checks for due posts every minute, so a post goes out within a minute or so of its time.
Scheduled posts go out whether or not anyone is signed in.
Cancelling a scheduled post
Cancel moves a scheduled post back to Drafts, with nothing sent. From there you can edit it, schedule it again or delete it.
Once a post has started going out it can no longer be cancelled. Check History to see how it went.
History
History shows the 120 most recent posts the workspace has sent, whether they went out in full, in part or not at all. Each row has a link to the post on every platform that took it.
Partly sent posts
A post is Partly sent when some platforms took it and others did not. The row shows each platform's outcome and, where it failed, the reason in plain words.
If an account was disconnected before its turn, that platform is marked Not sent.
Retrying a failed post
Retry on a failed or partly sent post sends it again to the platforms that did not take it. Platforms that already have it are skipped, so nothing is posted twice.
One case is held back: when a platform answered as if it had taken the post but gave no reference for it, the post may already be live there. That platform stays failed for you to check by hand.
In the composer, when Post now is only partly successful, the accounts that took the post are deselected, so posting again only retries the rest.
Times and time zones
Lists, History and analytics show times in the workspace's time zone, set in Settings.
The date and time you pick in the composer is read in the workspace's time zone, the same zone every list and the Auto-poster use, so a post set for 9:00 goes out at 9:00 there wherever you happen to be. You set the zone under Settings, General.