Report history

The report history table shows every report your organisation has run, so you can see what was generated and re-download the results.

The history table

1. Open Reports → History.
2. The table lists each run with its serial number, report name, a summary of its parameters, the user who triggered it, when it was triggered, its status, and when it completed.
3. Runs are ordered newest first, and each row carries a status badge that reflects the live state of that run.
4. A completed run offers a Download action; runs that are not yet complete (still pending, processing, or that failed) do not.

Only your own organisation’s runs appear here, you never see another organisation’s runs.

📷 Image placeholder

Add a screenshot here: the Report history table showing several runs with their serial number, report name, triggering user, timestamps, and coloured status badges, with a Download action on a completed row.

Filter the history

Narrow the table to find a specific run. Filters combine (all applied together) and stay within your organisation.

1. Filter by report name to see only the runs of that report.
2. Filter by status, pending, processing, completed or failed, to see only the runs currently in that state.
3. Filter by the user who triggered it to see only that person’s runs.
4. Combine any of the filters, a run has to match every condition you set. All filtering stays within your own organisation.
5. Clear the filters to return to the full list.

📷 Image placeholder

Add a screenshot here: the history filter controls (report name, status, and triggering-user pickers) with the table below narrowed to the matching runs.

What you can see

The triggered-user filter respects your permissions. Without the “view all runs” permission you only ever see your own runs, no matter how you filter. More generally, a report never shows you more than you are allowed to see in the underlying module, rows outside your data scope are excluded, and masked fields (such as cost) stay masked.