Scheduled

Scheduled lists every item that has a publish time and has not gone live yet — drafts and items still in review. Open it from the sidebar under Workflow → Scheduled; the sidebar shows it to people who hold Publish. Use it to see what is about to reach operators, move a publish time, or cancel one.

Schedules are set on the item itself. For that, follow Schedule a publish; this page documents the queue. To see the same schedule laid out by day, and drag items between days, use the Calendar (opens the admin console).

Times and your time zone

A line above the table names the zone the page works in — its full name with a short form beside it — and adds "Changes apply when you confirm them." That zone is your own time zone from your profile (Account settings → Profile), or your browser's if you have not set one. It is not an agency-wide setting. Two people in different zones see the same moment, each on their own clock — a publish at 06:00 in Brisbane reads as 04:00 to a colleague in Perth.

Every time you type on this page is read in that zone, too.

Columns

Items are listed soonest first.

Once the time has passed, Goes live shows processing… in red. Normally that lasts under a minute, until the next publishing run picks the item up. If the item is still here a few minutes later, the job is skipping it: Goes live shows waiting, with the reason underneath — see "When an item is held back" below.

A row with no recorded scheduler carries "Not scheduled by a publisher — reschedule it to queue it." from the start, even before its time comes. It will not go live until someone who holds Publish reschedules it.

Reschedule

Change the date or time in the Reschedule field. A tick button appears beside it as soon as the value differs from the saved one. Nothing is saved until you select the tick — tabbing away or leaving the page changes nothing. When you select it, the new time is saved and the list re-sorts.

• Rescheduling needs Publish: the field is disabled without it, and the database refuses the change from anyone else. Saving a new time records you as the person who scheduled the item.
• Emptying the field does not cancel the schedule; the tick stays disabled. Use Cancel instead.
• A time in the past is accepted, and the item is published at the next run, within a minute — unless it is held back.

Cancel

The cross button at the end of the row cancels the schedule straight away — there is no confirmation. Cancelling never publishes anything, so it needs only Edit content. The item keeps its status (Draft or In review), leaves this queue, and nothing reaches operators. To schedule it again, set a new time on the item.

What happens at the scheduled time

A database job runs every minute and publishes each queued item whose time has passed. It publishes the item as it stands at that moment, whether it is a draft or still in review — the review does not have to be finished first. It does check that the person who scheduled it can still publish, and two-person sign-off, both described below. (Sending an item back with Request changes clears its schedule, so a bounced item cannot go live on the old time.)

When the item publishes:

• Its status becomes Published and it leaves this queue.
• Operators' apps download it the next time they sync, and it stays readable offline — see how offline sync works.
• A push notification is queued for operators: "New in ROK" with the item's title. It goes to every active member who has not switched notifications off, limited to the guides each person chose to hear about.
• If delivery fails, the push is retried after 1, 2, 4, 8 and then 16 minutes. If every attempt fails, ROK's platform team sees it as undelivered. Delivery is at-least-once, so an operator may occasionally get the same push twice.
• If the item was unpublished again before the push went out, no push is sent.

When an item is held back

The job makes two checks before it publishes an item:

• The person who scheduled it still holds Publish in your agency. Someone removed from the group that gave it, or suspended, can no longer publish, and nor can their schedules.
• Two-person sign-off: the item's own Required box and any approval policy that matches it, counting approvals on the current version from people other than the author and the person who scheduled it. On the scheduled path the scheduler is the publisher, so their own approval does not count, just as it would not if they pressed Publish.

An item that fails either check is skipped, not failed. It stays in this queue, and the job looks at it again every minute — once the problem is fixed, it publishes at the next run.

A row showing waiting carries one of two reasons:

If the content no longer matters, cancel the schedule instead.

When the page is empty or fails

• Loading… shows while the queue loads.
• Nothing scheduled. Set a publish time from any draft to queue it. means nothing is waiting on a clock.
• If the queue cannot be loaded, the error message appears in place of the table.

Live updates

The list refreshes itself when content in your agency changes, so a row disappears the moment the job publishes it. This depends on Live updates being switched on in Settings → Features (opens the admin console). With it off, reload the page after a scheduled time passes to see what went live.