Content
Publishing schedule
Release an exact saved revision later, interpret times and recover blocked scheduled work.
What scheduling does
Scheduling records an intention to publish an exact saved revision at a future instant. It does not arrange to publish whatever draft happens to be newest at that time. This is useful for an announcement, event page or prepared design update whose release time is known in advance. An existing published version can remain visible while the replacement waits.
The background worker processes the intention without needing a visitor to open the site. Closing your browser does not cancel it. However, the worker must be running and able to reach the database. If the operator pauses or stops it, due work cannot complete until processing resumes; the scheduled time is not a guarantee independent of the application's operation.
Sources: Resource editor; Content and publication service; Publication and worker integration tests.
Schedule a saved entry
- Open the entry you have permission to publish. Finish its content and required relationships, then wait for Saved.
- In Publishing, choose Schedule publication. The control is disabled while there are unsaved changes.
- Set Date and time in the timezone shown by the dialog. Choose a future time and resolve any offset choice or invalid-time warning.
- Review the reminder that the currently saved revision will publish. Choose Schedule publication in the dialog to record the intention.
- Open Publishing schedule, find the row and confirm its title, due time and pending state.
Scheduling requires the same resource-specific capability as publication. An author may schedule their own Post; a contributor cannot schedule publication. Designers may schedule design resources they can publish, but not ordinary content merely because they can read it. Required fields and dependencies are checked when scheduling, then checked again when the worker executes.
Sources: Resource editor; Local date and time input; Content and publication service; Resource permission policy.
Read local time and daylight-saving choices
The input uses your browser's local timezone and shows its name. Site settings timezone does not override this input. GroCMS stores an exact instant so that two people in different timezones refer to the same scheduled event, even when their clocks show different hours. Read the displayed timezone rather than assuming everyone sees Johannesburg time.
A daylight-saving change can make a local clock time occur twice or not exist at all. For a repeated time, choose the offered UTC offset identifying the intended occurrence. For a time inside a skipped interval, choose a valid alternative. GroCMS prevents saving an unresolved time instead of silently guessing.
Sources: Resource editor; Local date and time input; Review and schedule screens.
Read the queue and its states
Search titles and choose Search to find the saved scheduled title. Filter by State, use Previous page or Next page for older work, and Refresh to reload current results. Open content takes you to the latest working draft; it does not silently replace the schedule's pinned revision with that draft.
| State | Meaning and next step |
|---|---|
| pending | Waiting for its due time or worker processing. Check the due time and worker if overdue. |
| published | The saved target was published successfully. |
| cancelled | Cancelled deliberately or superseded by a later schedule/publication/lifecycle change. |
| blocked | Authority or current publication state changed; review the entry and create a new schedule. |
| failed | Processing could not complete within the retry policy. Read the error and involve the operator if necessary. |
The optional Note field in the entry's action dialog is not currently shown or stored as a schedule description. Put essential editorial instructions in an appropriate review note or communicate them through the team's agreed process; do not rely on that optional field as a scheduling brief.
Sources: Review and schedule screens; Overview and workflow queries; Content and publication service; Publication and worker integration tests.
Edit, cancel or replace a schedule
Later saves remain a working draft and do not retarget the schedule. For example, schedule an announcement for Friday, then draft a longer version on Thursday: Friday still publishes the originally scheduled revision. To release the longer version instead, save it and schedule that saved revision again. The previous pending schedule becomes cancelled.
Use the row's cancel control for a pending intention when it should not run. Cancellation does not withdraw content that already published; use Unpublish content for that separate task. A newer manual publication, trash action or other publication lifecycle change cancels an older pending intention so it cannot unexpectedly overwrite the new decision.
Execution rechecks the scheduler's current account and publication rights. Disabling that person, removing their capability or changing required publication conditions can prevent release. Correct the reported issue, inspect the latest saved content and create a new schedule rather than repeatedly retrying an old assumption. Temporary worker failures may retry automatically, but the interface does not provide a universal Retry job button.
Sources: Review and schedule screens; Content and publication service; Publication and worker integration tests.