Skip to main content

Schedule recurring exports on any cadence

Set up a daily, weekly, or any-interval export that lands in Stateable storage or your own S3 bucket automatically.

Written by Rich Schaeffer

Manual exports are fine for one-off pulls, but if your team needs the same file every Monday morning, schedule it. Stateable runs the export on your schedule, delivers it to the destination you choose, and keeps a history of every run.

How to schedule an export

  1. Click Export in the top bar and open the Scheduled Export tab.

  2. Pick a cadence — daily, weekly, monthly, or a custom cron expression. Stateable schedules down to the minute.

  3. Pick a timezone. The schedule runs at the chosen local time regardless of daylight saving time changes.

  4. Set a filename template (e.g. commissions-{date}.csv). Date tokens are evaluated in the schedule's timezone.

  5. Choose the destination:

    • Stateable storage — your file is stored in a Stateable-managed S3 bucket. Downloadable from the Exports tab for 30 days.

    • Your own S3 bucket — delivered directly to your infrastructure (see the related article).

  6. Save the schedule. The next run time appears in the history panel.

Filters and fields

A scheduled export captures the filters and field selection you configure in the schedule — not the filters in your live grid. Changing your live grid later doesn't affect what the schedule pulls. If you need to update the schedule, edit it directly.

Run a schedule manually

Open the Exports tab, find the schedule, and click Run now. The run appears in history alongside its automatically-triggered siblings.

Troubleshooting

  • The schedule runs an hour early or late — double-check the timezone. Daylight saving switches are common culprits; Stateable honors the zone you selected.

  • Destination delivery fails — the run is marked failed in history. For external S3, re-test the connection in the Integrations tab.

Related

  • Run a one-off export from a filtered view

  • Send scheduled exports to your own S3 bucket

Did this answer your question?