Schedules

A schedule starts a published scenario automatically. First get the right result with a manual run, then enable automation.

Configuration

1. Select a scenario and give the schedule a clear name, such as Catalog in the morning and evening.
2. Choose a frequency or enter a cron expression.
3. Set a time zone. For Moscow time, use Europe/Moscow.
4. Check the next runs in the schedule preview.
5. Choose what happens when runs overlap, then activate the schedule.

Cron examples

Times are interpreted in the schedule's own time zone. If an allowed time window or random delay is configured, the actual start may differ from what the cron expression alone suggests.

Overlaps and pauses

If a task takes longer than the interval, choose a suitable overlap policy. Avoid building up a queue unnecessarily. Pausing stops future automatic runs; cancel an active run separately on its page. Run now lets you check it without waiting for the next scheduled time.

The schedule event history distinguishes a missed start from a failed execution. Automatic tasks use the same permissions and resource limits as manual ones. When the budget runs out, work may stop until it is topped up or a new billing period begins.

Choose a city

Search the City and time zone field by city, country or IANA name. You do not need to know a technical zone identifier: Perm and Yekaterinburg share a zone, while San Francisco selects US Pacific Time. The list includes major cities worldwide. Seasonal clock changes are automatic. Planned times and run history use the selected zone, even when you view the application from another country.

Retry a failed run

Keep the site rules, disable retries, or choose one to five additional attempts with a delay. Retries help with connection failures and temporary source outages. Code errors and access restrictions need your attention and are not retried. A retry continues from the saved state and does not replace the next calendar run.

Schedule details

Open a schedule to see five upcoming times and its five most recent runs. Each run shows its actual state: queued, running, successful or failed. A failure includes its reason and the retry time when one has been scheduled. Open a run or the associated script directly from this panel.

States refresh automatically every few seconds. Before the scheduler confirms a start, the panel displays an expected start rather than claiming the run is already executing. A connection error marks the last snapshot as outdated. Stop an existing run or queued retry in its run details: pausing a schedule prevents new automatic assignments, and does not cancel those already queued.