Guide

Track SQL runs, restore versions, and rerun exports with confidence

Q: What does SQL run history track?

Run history tracks each execution with status, duration, timestamps, and the related CSV/Excel export so teams can audit what ran and what file was produced.

Q: How do I find exports from a scheduled job?

Open the schedule run history dialog. It lists runs, variables used, notifications, and download actions for every exported file.

Q: Can I restore past SQL and rerun it?

Yes. Versions let you restore a previous snapshot and rerun with the same inputs, so you can reproduce exports reliably.

Run history is your audit trail. It connects the SQL you executed, the inputs you used, and the file your team downloaded so nobody has to guess which export is “the latest”.

Start free No credit card required. See the query workspace

Best practice: Treat run history as the source of truth for “what ran” before you schedule recurring exports.

History drawer

Open the history drawer to review every execution with status, duration, timestamps, and the related export. When a run produces a CSV or Excel file, the download action stays with that run so you can retrieve it later.

Size: 1600x900 (retina) - crop to 1200x630 for OG.

Run history dialog for schedules

Scheduled jobs link to a run history dialog that shows each run, its notification, the variables used, and the exported files. This is the quickest way to confirm what your schedule produced before you share the download.

Size: 1600x900 (retina) - crop to 1200x630 for OG.

Restore SQL and rerun with the right inputs

Versions help you restore a past snapshot of SQL and rerun it with confidence. If your query relies on variables, history makes it clear which inputs were used-so you can reproduce the same export setup without guesswork.

Versions & workspace Scheduling & run history