Autopilot & Publishing
How HarperFlow spreads freshly written articles across future publish times instead of releasing them all at once.
No article HarperFlow writes ever publishes the moment it's created. Every one gets a real, specific slot in the future, and this article covers how those slots get chosen.
Publish times land within your plan's cadence: the days of the week and business-hours window your schedule is set to, in your project's own timezone. Within that window, HarperFlow adds a bit of randomness to the exact minute so a batch of articles doesn't all land at the identical time.
A sparser cadence (say, two days a week) spreads across a longer window than a dense one (every weekday), so there are always enough eligible days to spread a batch across without doubling up on any one of them.
If you trigger a run while another batch is already scheduled, the new slots start after your most recently scheduled article for that project, not from the moment the new run began. Back-to-back or overlapping runs cascade forward in time instead of piling multiple articles onto the same slot.
An autopilot tick requests roughly your plan's monthly quota divided across however many times your cadence fires in a month, so a single tick doesn't spend the whole month's budget at once. A manual "write everything remaining" batch works differently: it spreads across whatever is left of your current billing period (at least a week, capped at 45 days) instead of a fixed week, since it represents the rest of what you're already paying for this period.
Tip: If you move one article's publish time by hand, the rest of the batch stays where it was. Reschedule any others individually from the Articles queue if you want to change more than one.