Schedules

A schedule is a five-field cron expression. The minimum interval depends on the plan: five minutes on free, sixty seconds on Pro, fifteen seconds on Business.

0 8 * * 1-5      every weekday morning at 08:00
0 */15 * * *     every 15 minutes
30 23 L * *      23:30 on the last day of the month

The timezone belongs to the schedule, not the workspace. The workspace only supplies a default so the field arrives filled in; from there each schedule carries its own. That is what lets the same report go out at 08:00 in São Paulo and 08:00 in Lisbon without duplicating the query.

UTC is never chosen silently. If a schedule is in UTC, it is because somebody picked UTC.

Every trigger records start time, duration, rows returned and the error when there was one. History is kept for the plan’s retention: 30 days on free, one year on Pro, three years on Business.

• The run is marked failed with the message the database returned, unrewritten.
• The schedule stays active; one failure does not switch a report off.
• If a failure alert is configured, it fires through the workspace’s alert route.