Playbooks
Set up a recurring announcement
Playbook: a weekly devlog that posts itself for a set number of weeks.
Stop a recurring announcement
Playbook: pause and edit, or let a schedule finish.
The schedule
You set the recurrence on the About tab, or when you first create the announcement.
A monthly send on a late day shifts to the last day of shorter months, so the 31st still lands in February.
Every schedule ends
A recurring announcement always runs for a fixed Number of sends. There is no open-ended option, and no end date. You give it a count, and it stops when it has posted that many times. When the last send goes out, the announcement moves to the Completed stage. It reads as done and stays read-only. Nothing more posts.The announcement lifecycle
How draft, published, unpublished, and completed fit together.
What your plan allows
Recurring announcements need Essential or above, and your plan puts two bounds on a schedule: how often it may repeat, and how many times. Essential allows weekly or slower, for up to 12 messages. Starter and Studio allow daily, for up to 52.Recurring limits by plan
The cadence floor and the message cap on every plan.
On Free and Indie you can draft a recurring announcement, but you cannot start its schedule. Publishing one there offers the upgrade.
Editing a running schedule
A published announcement is read-only, so you cannot change a schedule while it runs. To adjust the cadence, the message, or the number of sends, unpublish it, make your change, and publish again.Related articles
Publish an announcement
Start the schedule and reserve its sends.
Track your announcement messages
Watch each occurrence, retry a failure, skip one.
Stop a recurring announcement
Unpublish to pause and edit, or let it complete.
Plans and limits
Recurring availability, cadence, and send caps by plan.