> For the complete documentation index, see [llms.txt](https://salsa-digital.gitbook.io/govcms-content-administration/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://salsa-digital.gitbook.io/govcms-content-administration/workflows/scheduled-publishing.md).

# Scheduled publishing

Scheduled transitions allows GovCMS users to set a date and time for a moderation state to transition from one to another.

This usually takes the form of **Needs Review** transitioning to **Published**.

### ⚠️ Important disclaimer ⚠️

While you can set a scheduled transition to take place at a set date and time, that's not the specific **TIME** that your change will be actioned.

This is due to a system called Cron that manages the scheduled tasks on the GovCMS hosting platform.

On a normal, standalone website, Cron may be configured to run every 5 minutes, meaning that anything that the website wants to schedule for the future will be actioned at some point every 5 minutes.

However, due to the scale of GovCMS, our Cron schedule is every **one hour**.

And again, due to the scale of GovCMS, we can't have all 400+ websites running a task at the exact same time as each other, as this would overload the platform.

So instead, each website is given its own unknown minute each hour when it runs its Cron tasks to even out the load on the platform.

What this means, is that if you schedule your transition to **Published** at 2:30pm, and your website's  minute happens to be set to 31, then your content will be published at 2:31pm.

However, if your website's minute is set to 29, then your content won't be published until 3:29pm.

All we can guarantee is that your scheduled transition will take place **at some point within 1 minute, and 1 hour from the time you set**.

{% hint style="danger" %}
Do not use scheduled transitions for time-sensitive information such as Budget-related content.
{% endhint %}

### How to schedule a transition

To schedule a transition for a page, browse to it and then select the **Scheduled transitions** tab in the page edit menu.

<figure><img src="/files/9plK6u4rve6TKyG5qF0p" alt=""><figcaption></figcaption></figure>

This will show a summary of the current transitions that are scheduled for this page.

Select the blue **Add Scheduled transition** button.

You'll be presented with the the list of revisions, as well as a dropdown list for which transition you want to schedule and what date and time.

<figure><img src="/files/pqUqkMgKIROCmk5iLqfV" alt=""><figcaption></figcaption></figure>

Select the options that you want and select the blue **Schedule transition** button.

You'll be returned to the list of transitions with your new schedule listed.

<figure><img src="/files/NvIZKoPurEEDhk12CJHu" alt=""><figcaption></figcaption></figure>

You can use the options in the **Operations** dropdown menu to reschedule or delete the transition. This doesn't delete the revision itself, just the schedule.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://salsa-digital.gitbook.io/govcms-content-administration/workflows/scheduled-publishing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
