How post scheduling works in PostSider

PostSider uses a durable scheduling engine to power its publishing system. Unlike simple cron jobs or in-memory timers, every scheduled post is persisted so it survives server restarts, crashes, and deployments. The worker attempts publication at the scheduled time, but provider outages, expired tokens, rate limits, validation failures, and disconnected channels can still produce an ERROR state.

​

Setting a Schedule

When composing a post, you can assign a publish time in two ways:

​

Immediate vs. Scheduled Publishing

You have two options when creating a post:

​

The Visual Calendar

The Calendar page gives you a full view of everything in your publishing queue. Each scheduled post appears as a block on its scheduled date and time.

• Scan your week or month at a glance to spot gaps or over-crowded days
• Click any post to open it and make edits inline

​

Editing a Scheduled Post

You can edit eligible draft and queued posts before publication. Published posts cannot be edited or rescheduled, and pending-approval posts must be approved or rejected rather than dragged into the queue. Changes to an eligible post update its scheduled job.

​

Rescheduling a Post

To move a post to a different time, open the post and update the date/time field, then save. PostSider reschedules the publish job to the new time instantly.

​

What Happens When Publishing Fails

If PostSider cannot publish a post - because of a network error, an expired token, or a platform-side issue - the post is marked as Error and an error message is attached to it explaining what went wrong. PostSider surfaces the failure clearly so you can diagnose it and act on it. When you see a failed post:

1. Read the error message to understand the cause
2. Fix the underlying issue (e.g., reconnect the channel, shorten the content)
3. Use the Retry action on the post to reschedule it

​

Rate Limits

Every social platform enforces its own API rate limits. PostSider uses durable Temporal workflows and provider-specific retry/backoff behavior, but it does not guarantee one universal spacing policy across every provider.

​

Queue plans

The queue plan defines when each channel publishes, so find-slot can pick the next free time automatically. Configure it under Settings → Queue Plan:

• Per-channel slots - set the times each channel can publish at (for example 09:00, 12:00, 18:00).
• Weekdays - choose which days of the week the slots apply to.
• Timezone - give a channel its own timezone. Resolution order: channel timezone, then the organization’s default timezone, then UTC.
• Team assignment - optionally assign a channel to a specific member.

The slot search is day-aware: GET /public/v1/find-slot/:id (and the composer’s queue picker) returns the next free slot for the current weekday, looking ahead up to 365 days.

​

Smart Slots

Smart Slots (“Suggest best time” in the composer) suggests a publish time by blending per-platform peak-hour heuristics with the channel’s own posting rhythm - the hours its published posts already use, once there are at least 8. It avoids times already occupied in the queue and suggests one time per local day.