Create and run reports
- Synopsis
- Full Details
In briefBuild a report in Administration › Reports from a Report Type, an Object, filters, columns and sort rules, save it, then View it and use Download Report for CSV or Excel (.xlsx). Saved reports are shared across your organization and run on demand.
- Checking a column adds it to the end of the column order; use Order Filters & Columns only for a specific arrangement.
- A date filter means the whole UTC day; After excludes the named day.
- Audit History needs a Category. An update is one row per changed value; a create or a delete
starts with one summary row,
Record Added: <name>orRecord Deleted: <name>. - Cancel beside the button stops a download that is running.
- Save is refused while a filter is turned on with no value, or one it cannot use.
- Workflow history lists each finished workflow run across days; Job history's Job Termination Status can match a list of statuses.
- An export that fails part-way saves no file. Run it again rather than looking for a partial one.
- Without Workspaces View, the Roles, Resources and Service Requests reports show workspace ids, and filtering on the workspace name is refused.
Reports answer questions about your automation — what's configured and what ran — and let you export the results. Operators and administrators both use them.
Questions about what's configured and what ran get answered by hand (screenshots, ad-hoc queries, spreadsheets), which is slow and leaves no repeatable record.
What you can report on
| Category | Examples |
|---|---|
| Configuration & Reference | Agents, calendars, frequencies, jobs, scripts, tags |
| Governance & Access | Audit History, roles |
| Operational Objects | Event Details, job history, properties, resources, service requests, thresholds, workflow history |
Build a report
To build and run a report, complete the following steps:
- Go to Administration › Reports and select New Report.
- On Create Report, enter a Report Name, then choose what to report on with Report Type and Object. A name already in use is flagged on the field: A report with this name already exists.
- Under Choose Filters, add filters to narrow the results (text, number, single-select, or date/time; for example, a date and an environment for job history).
- Under Choose Columns, select the columns you want.
- To set the sort and column order, select Order Filters & Columns, add up to five rules with Add New Sort Rule, drag the columns under Column Order, and select Save.
- Select Create Report. A report runs once it is saved. If a filter you turned on has no value, or one it cannot use, the save is refused: Some filters are incomplete or invalid. Fix them or turn them off to save. Fill in or turn off each filter that shows a problem.
- On Reports, open the report's actions menu and select View to see the results, then use Download Report to export to CSV or Excel (.xlsx) if needed.
Checking a column adds it to the end of the column order automatically, so you only need Order Filters & Columns when you want a specific arrangement. Earlier builds could leave a checked column out of the order, and because results and exports follow the order, the column then showed in neither; a report saved in that state fixes itself the next time you open it.
Two filters that used to mislead
Both of these returned wrong results without any error, so a report built on either looked legitimate. If you have saved reports using them, re-check what they return.
Date filters now mean the whole day. A date filter takes a date while the values it matches are timestamps, so a date now means the entire day it names, in UTC — which is how the report's own date columns are labelled.
| Operator | Matches | What changed |
|---|---|---|
| On | Anywhere within that day | Used to match nothing — only a value stamped at exactly midnight qualified. |
| Between | Start of the from day through the end of the to day | Used to stop at midnight of the to day, dropping that whole day's rows. |
| Before | Strictly earlier than that day | Unchanged. |
| After | Strictly later than that day | Used to include the named day; it now excludes it. |
On, Before and After against one date now cover the timeline exactly once each. Note After is the one that returns fewer rows than before — add an On filter as well if you meant to include the day itself.
Is empty finds blanks that it used to miss. A text value can be blank either by holding an empty string or by never having been set, and the two look identical on screen. Is empty now matches both and Is not empty excludes both. On the Jobs report's Documentation filter and the Scripts and Roles reports' Description filters that is a large change: almost every job stores the empty-string form, so Is empty used to find close to nothing and Is not empty used to return everything, blanks included.
Save it for reuse
A saved report keeps its columns, filters, and sort, so you can select View again whenever you need it. This is handy for a recurring month-end or compliance pull. Copy in the actions menu starts a new report with the same filters and columns under a name you choose. Columns the report type no longer offers are left out; if none are left, the copy is saved without columns, and you edit it to choose some before you view it.
The Audit History report, under Governance & Access, lists one row per changed value: what changed,
its before and after, who changed it, when, and in which environment. A create or a delete starts
with one summary row instead: Record Added: <name> in After Value, or Record Deleted: <name>
in Before Value, with the kind of record, such as Calendar Record, in Data Changed. A
calendar, property, threshold, resource, agent, agent pool or role then lists one row per value.
Filter After Value Contains Record Added to list what was added. Choose a Category (or All
Categories) to run it, and add a Changed At range to keep a large history quick. It needs Audit
History View, shows the first 10,000 rows on screen, and downloads up to 100,000. See
Reports.
- Results are paginated and large sets show a truncation note; exports stream the full set, so a large Excel (.xlsx) download finishes as well as a CSV one. A Jobs report reads only the page you view, so it loads on a large tenant too, and its download is sorted like the results; one over 100,000 rows is refused. See Jobs: large tenants.
- While a download runs, select Cancel beside the button to stop it; no file is saved.
- An export that fails part-way saves no file: the page says The export did not finish, so no file was saved. Run it again. See Saved reports, results, and export.
- An open report does not refresh when you come back to its browser tab. Change page or open the report again for current rows.
- Job history's Workflow Name, Job Name and Agent Name filters take a
*wildcard:payroll*is starts-with,*payrollis ends-with, and a value with no*still matches anywhere in the name._and%are literal now, so a filter ofJOB_01no longer brings backJOB-01as well. See The Processes page. - Job history has an Instance Name column and filter, for workflows that build as several named schedule instances per date. Filter it with Is empty to get only the workflows that don't. Note that Workflow Name in this report is the plain workflow name — the instance is in its own column, so you can paste a workflow name straight back into the filter.
- Job history also has Agent Pool and Event Triggers columns and filters: the pool or
legacy agent group each job was assigned to, and the events it raises with the condition for each,
such as
Job Status: Failed → $NOTIFY:EMAIL. Filter Event Triggers with Contains$NOTIFYto find every job that sends a notification. See Job History: Agent Pool and Event Triggers. - Job history and Event Details need a Date filter, which offers On, Before and After as well as Between. A run that takes longer than 25 seconds asks you to narrow the date range. A Job history download is sorted the same way as the results; a sorted one over 100,000 rows is refused. See Job History and Event Details: the Date filter.
- Job history's Job Termination Status offers Is any of and Is none of, which take a list. Is none of with every waiting and running status leaves only the jobs that finished.
- Workflow history lists one row per finished workflow run, Completed or Cancelled, across any range of dates, with its start, end and run time, its job count and how many jobs failed. It needs an Environment and a Date. See Workflow History.
- The Frequencies report lists each frequency's own dates, the same ones its forecast shows: Monday to Friday, with no holidays. It has no workflow column, so to see when a workflow will run use the workflow editor's Forecast view.
- The Agents report can show Operator State and Effective Status, for agents deliberately taken out of service. To list agents that can actually take work, filter Operator State is Active — filtering on Status alone won't do it, since a Marked Draining agent is usually still connected.
- The Jobs report can show Agent, Workspace and Workflow Start Time columns plus
Start Offset, Late to Start Offset, Start Time, Late to Start Time, Estimated Run
Time and Max Run Time — which answers "where does this run, and when is it meant to?" in one
pull. Start Time reads like
Same day at 02:30or+1 day at 01:15, and the run times are in whole minutes. The six timing settings belong to a job frequency, so selecting any of them returns one row per frequency and brings Frequency Name along automatically; unselect Frequency Name and the timing columns come off with it. A pool or a legacy agent group is labelled as such in the Agent column, so a bare name is a real agent. - Set the Jobs report's Include Jobs Other Workflows Depend On filter to Yes to list each job under every other workflow that depends on it, too. Owning Workflow names the workflow the job belongs to. See Jobs: jobs other workflows depend on.
- The Roles, Resources and Service Requests reports may show workspace ids instead of names. Reading the workspace list is its own permission (Workspaces View), so without it one of these reports runs but shows ids where it would show names — and filtering or sorting on the workspace name is refused outright rather than matching nothing. Exports behave the same way. If a report's workspace column looks like identifiers, that is the permission to ask for.
- The Roles report is the access review in one pull: every role, its permissions, the workspace
and environment pairs it applies to, and whether it is a built-in system role. Two columns read
differently from how they look. Permissions names each permission, such as
Workflows: View, and can list more than you picked, because granting any action also grants that object type's view permission, where it has one. AndAnyin a Scopes pair means the role is unrestricted on that axis —Payroll / Anyis every environment, not a blank. Filter System Role is No to see only the roles your team created. - The Service Requests report is the quickest way to review a self-service catalog: it lists every request with its tags, workspace, version, and how many inputs and events each one carries. Sort by Inputs to find the requests a requester is most likely to fill in wrongly.
- Reports are read-only: running one never changes anything.
- Reports run on demand. Neither a report nor a saved search is delivered on a schedule or by email — run it and export the result when you need it.
- Saved reports are shared: everyone in your organization who can open Reports sees the same list, so give each one a name others will recognize. A name can be used only once.
Related topics
- Reports — full configuration reference and troubleshooting
- Use the event log (Operator)
- Search across OpCon Continuum (Operator)