Set the cadence and time

Three cadences to choose from

When you create an autopilot, you give it a name and pick how often it should fire. There are three choices: Daily, Weekdays, and Weekly. Daily fires every day, Weekdays skips Saturday and Sunday, and Weekly fires once a week. Next to the cadence you set a time of day in HH:MM, which starts at 9:00 unless you change it.

That pair, cadence plus time, is the trigger. It is the moment the task wakes up and builds its next batch of posts.

It runs in your project timezone

The time you type is local to the project, not to wherever the server sits. Set your project timezone correctly and 9:00 means 9:00 for your audience. The scheduler quietly converts that to the right instant behind the scenes, so you never have to think in UTC.

How firing actually works

A background job checks for due tasks every minute and claims each one safely, so a task fires exactly once even when several servers are running at the same time. After a task fires, its next run time rolls forward to the following slot on its own. You set the rhythm once, and the task keeps its own place in line. It also respects quiet hours, so it will not fire in the middle of the night.

Match the cadence to your pool

Think of the cadence like the tempo of a song: faster tempo, fewer bars before it repeats. Daily burns through a pool faster than Weekdays. If you only have a handful of creatives, a lighter cadence or a shorter window keeps the calendar from repeating itself. You can always pause and recreate with a different rhythm later.