DataPilot

Guide

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

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.

Screenshot placeholder

Add screenshot: history drawer showing a run list with status, duration, and a download CTA.

Screenshot needed

Screenshot needed: history drawer showing a run list with status, duration, and a download CTA.

Sizes: 1600x900 hero + OG 1200x630; Alt: "SQL run history drawer with download action".

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.

Screenshot placeholder

Add screenshot: schedule run history dialog with run rows and download buttons.

Screenshot needed

Screenshot needed: schedule run history dialog with runs, statuses, and download buttons.

Sizes: 1600x900 hero + OG 1200x630; Alt: "Schedule run history dialog with download actions".

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