Scheduled publishing
Scheduled publishing lets a publisher choose when a change goes live. You can schedule a draft to publish, or a live entry to unpublish, at a set time on the production branch. At that time Quant commits the approved change, builds the whole site and publishes it, so nobody needs to keep a browser open.
Scheduled publishing works the same way on QuantCDN and QuantGov.
Turn it on
Section titled “Turn it on”A user with the manage_studio permission turns scheduling on for each project.
- Open Settings from the gear icon in the Studio nav rail.
- On the General tab, find the Scheduled publishing card and turn on Allow scheduled publishing.
- Choose the Time zone and click Save. Publishers enter schedule times in this time zone. The default is
Australia/Melbourne.
When you turn scheduling off, schedules that have not started yet do not run. Their status becomes Pending review instead.
Schedule an entry
Section titled “Schedule an entry”You need the publish_studio permission, which the Studio Content Publisher, Studio Manager and organisation roles include. See Permissions and roles.
- Open the entry on the production branch.
- Make your changes and click Save draft. A schedule publishes the saved draft, so save it first.
- Click Schedule publish…. For a live entry you want to take down, click Schedule unpublish… instead.
- Pick a date and a time, then click Schedule. Times are five-minute slots in the project’s time zone, and the slot must be in the future.
The editor then shows the schedule, for example “Scheduled to publish Sun 22 Nov 2026, 6:55 pm AEDT by Alex Smith”, with a Cancel schedule button. Each entry has one schedule at a time. If you schedule an entry that already has one, Studio asks you to confirm that the new time replaces the old one.
The Scheduled screen in the Studio nav rail lists every schedule on the site with its entry, action, requested time, status, start and finish times and the person who scheduled it. Publishers can cancel a schedule there until it starts.
Drafts that would fail the build
Section titled “Drafts that would fail the build”Before Studio saves a schedule, it checks the saved draft against the collection’s schema. If the draft would fail the site build, Studio refuses the schedule and shows the field and the reason, for example:
readingTime: Expected type "number", received "string"Fix the field, save the draft and schedule it again. The live preview does not run this check, so a draft can look correct in the preview and still be refused here.
What happens at the scheduled time
Section titled “What happens at the scheduled time”Shortly after the slot, Quant:
- Checks that the entry, its draft and the publisher’s permission are the same as when it was scheduled.
- Commits the change to the production branch.
- Builds the whole site and publishes it.
Expect the change on the live site a few minutes after its slot, because the run builds and publishes the full site. Only one full publish runs on a site at a time, so a scheduled run waits if someone is running Build & Publish.
Once a schedule has started, it cannot be cancelled.
When a schedule does not publish
Section titled “When a schedule does not publish”Review
Section titled “Review”A schedule publishes exactly what was approved. If something changed after it was scheduled, it does not run, and its status becomes Pending review. This happens when:
- someone edited the draft or the live entry,
- scheduling was turned off for the project,
- the person who scheduled it no longer has the
publish_studiopermission, - or the site build rejected the change.
The Scheduled screen shows the reason under the status, with a support reference where one applies. A publisher checks the entry and schedules it again.
Failures
Section titled “Failures”If GitHub or the builder is unavailable, Quant tries the run again a few minutes later. A run that still fails is marked as failed, with a support reference.
If a run stops after its commit reached the production branch, the message says the changes are on the site’s branch but are not live. Publish the site (Deploy, or Build & Publish with Quant Builder) to make them live. You do not need to schedule them again.
When a schedule goes to review or fails, Quant emails the person who scheduled it and every member with the manage_studio permission. The email names each entry and its slot, gives the reason and links to the project in Studio.
Scheduling is available in the dashboard only. The Studio API has no schedule endpoints.
Next steps
Section titled “Next steps”- Review and publishing: how drafts, reviews and publishing fit together
- Deployments: watch a publish and use Build & Publish
- Permissions and roles: who can schedule and who can turn scheduling on
