How background scheduling works

Version: 1.0.0 · Released: 2026-09-08

Route: Conceptual guide (dashboard /; production cron endpoint on the server)

Who can access

Useful for all trainees. Changing schedules in the UI requires Admin or Editor. Operating production cron is an administrator task.

Screenshots

There is no dedicated PNG for this topic. These related views show the queue and workspace:

What this page does

Explains what happens after you click Schedule or Schedule all: the post is stored as Pending, then published when its time arrives.

Layout at a glance (concept)

Schedule in UI
    → Pending entry in Upcoming Posts
    → Time reaches schedule (Pakistan / PKT)
    → Publish to Facebook & Instagram (production)
    → Status becomes completed (leaves Upcoming Posts)

Steps — user perspective

1. Schedule one product or use Schedule Collection.
2. Confirm the item under Upcoming Posts with a Pending badge and … PKT time.
3. Optionally edit or remove it before publish time.
4. When the time is due:
   • Production: A background job (cron) checks every minute and publishes due posts.
   • Demo Mode: Due posts complete automatically in the offline sandbox so you can see the flow without cron setup.

Production vs Demo Mode

Permissions

Errors & edge cases

• If a production post stays Pending past its time, check that the cron job is running and Meta credentials are valid.
• Wrong clock or timezone on the server can delay publishes — UI times are Pakistan (Asia/Karachi).
• Deleting a pending post removes it from the queue; the product can become schedulable again.
• Demo Reset demo clears sandbox posts and schedules for the current account.

Related links

• Single product scheduling
• Bulk schedule collection
• Upcoming posts
• Introduction