Scheduled publishing
Give a record version a publish time and Fóir publishes it then. Add an unpublish time for content that should come down again.
A schedule belongs to a version
A schedule is set on one specific version of a record, and that version is what gets published at the chosen time. The record stays in its current state until then. You can change or cancel a schedule at any point before it fires. To publish several records at the same moment, group their versions in a rollout.
Publish and unpublish times
An unpublish time can be set alongside the publish time, for content with an end date: publish on 1 June, unpublish on 30 June. The unpublish time has to be after the publish time, or the request is refused.
Where you set one
In the console, open the version, choose Schedule next to Publish, and pick a date and time. You enter it in local time and it is stored as UTC. The Scheduled view under Content lists everything queued across the project and filters by model, date range or status.
The CLI has foir records schedule-publish and a matching cancel command. GraphQL generates a schedule mutation and a cancel mutation for each model with publishing or variants on, and an agent connected over MCP has tools for both. Scheduling needs the records:publish permission.
When the time comes
A background worker carries out the publish when it falls due. A version that is no longer scheduled at that moment is skipped. A publish that still fails on its final attempt has its schedule withdrawn, so no version is left showing a schedule that will never run.
Read the detail
The scheduled publishing guide walks through setting, changing and cancelling a schedule, and the view of everything queued.