Running Reports and Interpreting Results

End-to-End Flow

Edit the SQL in the editor and adjust report settings such as name, output format, and parameters.
Save the report. Unpublished is fine while validating.
Run in the editor. Results appear in the grid with interactive row limits, typically 10,000 rows. Use this step to validate logic and output shape.
When satisfied, publish the report so it appears in the standard Report List.
Run from the Report List. Open the report from the list, supply parameters if prompted, and run. This is the run path your audience will typically use.

Running in the editor and running from the Report List use the same report definition. The difference is where you launch it and whether you are in a rapid design loop or executing a published report.

Interactive Runs (In Editor)

Interactive runs are ideal for fast validation loops while designing logic. Results appear directly in the grid, and interactive row limits apply.

Long-Running Queries

Longer or heavier queries may move to background processing. Use background execution when moving from design-time checks to operational-scale output.

Result Validation Checklist

Before publishing, confirm that:

Row count is plausible for the selected scope
Time filters and parameter substitutions are correct
There are no duplicate-grain surprises from joins
Key totals align with known business expectations