> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superlaunch.pro/llms.txt
> Use this file to discover all available pages before exploring further.

# Schedule recurring launches

> Set recurring timing, selection behavior, and batch limits.

A recurring schedule prepares launches from saved configuration. You need scheduling access as well as the permissions required for the launch.

## Create a schedule

1. Open launch setup.
2. Choose **Test new creatives** and a saved template version.
3. Choose a collection and review its selection behavior.
4. Select recurring timing.
5. Set the frequency, time, and **Schedule time zone**.
6. Set the batch count and budget limits.
7. Review whether created objects stay paused or activate.
8. Save the schedule.

The schedule time zone determines when the recurring job starts. Provider delivery settings in the template are separate.

## Check saved settings

The schedule uses specific template and collection versions. Review them before saving; editing a template later does not update the version selected by the schedule. Runs that have already started keep their original settings.

Superlaunch skips overlapping and missed runs. Each new run checks creative approval, access, billing, and limits before launching.

## Pause, edit, and inspect

Open the schedule to inspect its current status and recent work. Read its lock version before an MCP update. Use `launcher_schedules_change_status` to change status and `launcher_schedules_update` to revise configuration.

Read the resulting launch and operation records after an occurrence. If it fails, review the reason before re-enabling or retrying.

See [Launcher MCP tools](/mcp/reference/launcher-schedules) for exact schedule fields.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.