Version history explains the logic evolution
Review past query states and restore earlier logic when you need to compare or recover.
Guide
Keep a visible history of what changed, what ran, and what got delivered.
Run history is where reporting trust becomes operational. DataPilot keeps query versions, execution history, variables, and exported files close enough that the team can stop guessing which run was the "real one."
Run history explains the execution trail
See when the query ran, whether it succeeded, and what outputs were produced.
Variables and files stay attached to the run
The value of run history is not just timing. It is knowing which inputs and which files belong to that specific execution.
FAQ
What is the difference between query history and run history?
Query history explains how the SQL changed. Run history explains when that logic executed, with which inputs, and what it produced.
Can I restore an older version of the SQL?
Yes. You can review earlier query states and restore a prior version when you need to compare or recover logic.
Can I trace which file came from which run?
Yes. DataPilot keeps the run trail close to the output so the team can map exported files back to the execution that produced them.