Reports
- Synopsis
- Full Details
In briefReports query the platform's configuration and history — agents, jobs, job history, roles, service requests and more — with the columns, sort rules and filters you choose, and export the result to CSV or Excel. A report can be saved and re-run, and saved reports are shared across your organization.
WhereAdministration › Reports. New Report opens the builder, where you choose the Report Type and the Object, then filters and columns.
When
- You need a list of configured objects with specific columns — every job with its agent and timings, every role with its permissions.
- You need to look back at what ran, with Job History, Workflow History or Event Details.
- You want an export to work with outside Continuum.
To find an object by name, use Global search instead.
How
- Open Reports and select New Report.
- Enter a Report Name, and pick a Report Type and Object.
- Choose filters and columns, and set the sort order.
- Save it, run it, and export the results if you need them. The full walkthrough is Create and run reports.
- A date filter means the whole UTC day it names; Before and After exclude that day.
- Is empty matches both an empty value and a value never set.
- Selecting a Jobs timing column returns one row per frequency and brings Frequency Name with it. Include Jobs Other Workflows Depend On also lists each job under every other workflow that depends on it, with Owning Workflow naming its own.
- Workflow History lists one row per finished workflow run, Completed or Cancelled, across any range of dates. Job History's Job Termination Status can match a list of statuses with Is any of or Is none of.
- Save is refused while a filter is turned on with no value, or one it cannot use. A column the report type no longer offers is left out of the results and the download.
- Reports are read-only and run on demand; there is no scheduled delivery.
- The Frequencies report lists every frequency's own pattern dates, as its forecast shows them: Monday to Friday, no holidays, with its exclusion and Annual Plan calendars applied. A frequency it cannot work out is named in a Some rows are not shown warning, with the reason.
- Job History can show each run's Agent Pool and the Event Triggers its job carries, and filter on either. Its Date filter, like the one on Event Details, offers On, Before, After and Between, and its downloads are sorted the same way as the results page.
- An export that fails part-way saves no file and says so. Cancel beside the button stops a download that is running.
- In Audit History, a create or a delete starts with one summary row,
Record Added: <name>orRecord Deleted: <name>, labelled with the kind of record, such as Calendar Record; an update is one row per changed value, and a list item it adds or removes is marked(Record Added)or(Record Deleted). A save that changes nothing on a deployment records nothing. A change made by an event a person sent is recorded under that person. Each z/OS JCL save is recorded too, without the JCL text.
- On some reports, such as Agents, a column is sorted over the fetched result rather than on the server, and an export does not apply that sort. Jobs, Job History and Workflow History exports do.
- A Job History, Workflow History or Event Details report that takes longer than 25 seconds asks you to narrow the date range; a Jobs report that takes too long asks you to narrow the filters.
- The Resources report's In Use counts every environment unless its Environment filter names one.
- A Status of Online includes agents marked out of service; filter Operator State too.
- An Audit History report needs a Category, takes it once, and refuses a filter it does not offer. It shows at most 10,000 rows; a download stops at 100,000.
Task walkthrough: Create and run reports. This page is the full configuration and troubleshooting reference.
Reports let users query the platform's configuration and history and export the results. A report is built by choosing columns, sorting, and filters against a chosen object; reports can be saved and re-run.
Report catalog
| Category | Objects you can report on |
|---|---|
| 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 |
- Key Columns
- Jobs
- Job History
- Workflow History
- Frequencies
- Service Requests
- Audit History
- Roles
- Tags
- Building a Report
- Saved Reports and Export
Key Columns
Columns worth knowing about
| Report | Column | What it does |
|---|---|---|
| Properties | Property Name | Filterable by Contains, Equals and Starts with, and each does what it says, on screen and in the download, ignoring case and any spaces before or after the value you type. A value of any length works. Earlier builds treated every operator as Contains, so Equals ENV also returned ENV_PATH and MY_ENV. A report saved through the API with another operator, or a value that is not text, on Property Name is refused when it is saved. |
| Properties | Value | Shows each property’s value, filterable by Contains, Equals, Is empty or Is not empty, and sortable. A value on an encrypted property is masked. The value of every property comes with the property list, so every row shows its value and a filter or sort covers every property; a row whose value was not returned reads (unavailable). Is empty finds the properties whose value is deliberately empty — an optional setting left unset; it does not match an encrypted property, or one whose value was not returned — both are excluded from a filtered result either way. |
| Calendars | Date | One row per date, replacing the old Date Count. Per-date detail is capped at 500 calendars — above that, run the report on a narrower selection. |
| Resources | In Use | Active allocation units for the resource, summed across every environment, unless the report's Environment filter names one: then it counts only that environment's allocations. Filterable by Equals, Greater than, Less than, and sortable; the filter compares the number the column shows. Compare it against Total to see remaining headroom. Total is shared by every environment, so the Environment filter does not change it, and it removes no rows. |
| Jobs | Job Type | Reports the job's actual type. Earlier builds read a field that did not exist, so every row came back Unknown; a job with no type still reads Unknown, and the filter now matches those rows. The values are internal type names — run-command, unix-command, windows-command — not the display names in the job type picker. |
| Agents | Operator State | Whether the agent has been marked out of service — Active, Marked Offline, or Marked Draining. Filterable and sortable. |
| Agents | Effective Status | The single value the agent lists show, combining observed connectivity with any operator mark. Available as a column and sortable in the report, but the sort is applied over the fetched result, so an export does not apply it. There is no Effective Status filter — filter on Status or Operator State instead. |
Status and Operator State are separate on purpose. A Marked Draining agent stays connected, so it still has a Status of Online. (Mark Offline stops communication with a legacy or Universal Agent, so such an agent usually reads Offline — see What Mark Offline does to communication.) Filtering Status is Online therefore includes agents that can take no work. To report on agents that are genuinely available, filter Operator State is Active as well.
Jobs
Jobs: agent, workspace and per-frequency timings
The Jobs report answers where a job runs and when it is expected to run. These columns carry that:
| Column | Reads | Shown as |
|---|---|---|
| Agent | The job's agent assignment | PROD-AGENT-01 for a single agent, PROD-POOL (Pool) for a pool, AllUNIX (Legacy Group) for a legacy agent group |
| Workspace | The workspace of the workflow the job belongs to | The workspace's name, or its id when your roles do not include Workspaces View |
| Workflow Start Time | The start time set on the workflow | The time of day, as set in the workflow's current version |
| Start Offset | The frequency's start offset, with its format | 02:00 (absolute) |
| Late to Start Offset | The frequency's late-to-start offset | 00:30 |
| Start Time | When the job is scheduled to start: the workflow's start time plus the start offset | Same day at 02:30, +1 day at 01:15, or 01:30 after workflow start |
| Late to Start Time | When the job counts as late to start: its start time plus the late-to-start offset | As Start Time. Empty for a job with no late-to-start offset |
| Estimated Run Time | The frequency's expected run time | Whole minutes, with no unit: 12 |
| Max Run Time | The frequency's run-time limit | Whole minutes, with no unit: 60 |
A pool and a legacy agent group are labelled, an agent is not. The three dispatch differently, and
a pool named PROD-POOL under a column headed Agent is otherwise indistinguishable from an agent of
the same name — so only the bare name is an actual agent.
Start Offset carries its format because the number alone is ambiguous. An offset is a duration
from the schedule date, so 02:00 means two hours in, not 2am — see
offsets past midnight. A job whose configuration is
missing the format shows the bare offset rather than asserting a base that was never stored.
Start Time and Late to Start Time are worked out from the job's configuration. A workflow that
starts at 22:00 with a job offset of 03:00 shows +1 day at 01:00. A job with no start offset
starts with its workflow, and a workflow with no start time counts from midnight. A relative
offset counts from when the workflow actually starts, which the configuration cannot know, so it
reads as a time after the workflow starts instead of a time of day. Times use the 24-hour clock.
These columns describe the workflow's current version as it is set. A deployment pinned to another version, or changed for one environment, can start its jobs at a different time.
The six timing columns return one row per frequency
Agent, Workspace and Workflow Start Time belong to the job or its workflow. The other six belong to a job frequency: a job on a Daily and a Month-End frequency has two start offsets and two run-time limits, and there is no single row they both fit on. So selecting any of the six expands the result to one row per (job, frequency).
Rows that differ only in timings read as corruption rather than as two schedules, so the frequency's name has to travel with them:
- Selecting a timing column also selects Frequency Name.
- Unselecting Frequency Name takes the six timing columns back off with it.
- A report definition that names a timing column without Frequency Name is refused with a message naming the missing column. The page never builds one, so this is only reachable by driving the API directly.
Agent, Workspace and Workflow Start Time do not trigger the expansion. Select them on their own and the report stays one row per job, with frequency names collapsed into a single cell as before.
The timing columns and Agent sort but do not filter — there is no Agent or Max Run Time filter. Every Jobs column sorts except Tags and Workspace, and the download is sorted the same way as the results page, by every sort rule.
It used to be compared as text, which ordered version 10 ahead of version 2. It is compared numerically now, so a Jobs report you already saved sorted by that column comes back in a different — and correct — order.
Jobs: jobs other workflows depend on
A workflow can depend on a job in another workflow. To see those jobs under the workflows that depend on them, set the Include Jobs Other Workflows Depend On filter to Yes.
- Each such job is listed once under its own workflow, as usual, and once more under each other workflow that depends on it. On that extra row, Workflow Name, Workflow Version and Updated At are the depending workflow's.
- Owning Workflow names the workflow the job belongs to. On a job's own row it is the same as Workflow Name; on an extra row it is the other workflow.
- A workflow that depends on its own job adds no extra row.
- With the filter off, or not set, the report lists each job under its own workflow only, as it always has, so reports saved before the filter existed return the same rows.
The Workflow Name, Workflow Version and Updated At filters test the workflow a row is listed under.
Jobs: large tenants
A Jobs report reads only the page you are looking at, already filtered and sorted. Earlier builds read every job before sorting, which could make a sorted report on a large tenant time out.
- A report that still takes too long stops with This report took too long to run. Narrow the filters and run it again.
- A download that would hold more than 100,000 rows is refused before it starts: This report has more than 100,000 rows. Narrow the filters and download it again.
- A filter saved with an operator the filter does not offer or a value of the wrong kind, or saved twice (other than Updated At, where each one narrows the dates), stops the report with a message naming the filter, rather than running it with that filter left out.
Job History
Job History and Event Details: the Date filter
Job History and Event Details each need an Environment and a Date filter. The Date filter offers Between, On, Before and After. In Job History it matches the job's schedule date; in Event Details, the date and time the event was received. A date means the whole UTC day, as in every report — see What a date filter matches. Before and After set only one end of the range, so they can cover a long stretch of history. Earlier builds offered Between only.
A report that takes too long asks you to narrow the date range. When reading the rows for the results takes longer than 25 seconds, or the service that holds them does not answer in time, the report stops with This report took too long to run. Narrow the date range and run it again. A download is not held to the 25 seconds.
Job History: matching several statuses
Job Termination Status offers Is any of and Is none of as well as Is and Is not. Each of the two takes a list: pick as many statuses as you need. Is none of is how you leave out every waiting and running job at once, so the report lists only jobs that have finished.
- A list with nothing picked counts as no value, so Save is refused until you pick one.
- Changing the operator between a one-status operator and a list operator clears the value.
- Reports saved with Is or Is not run as before.
Job History: five columns from the instance itself
Job History gained Frequency, Tags, Documentation, Start Offset, and Latest Start Time.
| Column | Filter operators | Notes |
|---|---|---|
| Frequency | Contains, Equals, Starts with | The frequency that triggered this instance. |
| Tags | Contains | The job's tags. |
| Documentation | Contains, Equals, Is empty, Is not empty | The job's documentation text. |
| Start Offset | Equals, Is empty, Is not empty | The configured start offset (HH:mm) for the triggering frequency. A job with no offset configured reads as empty, so Is empty is meaningful. |
| Latest Start Time | On, Before, After, Between | The latest allowed start time for the instance. |
All five are build-time snapshots of the instance, not a live look-up. Each instance is built from exactly one matched frequency, so these report what that instance was built with — change the job's design tomorrow and yesterday's rows keep yesterday's values.
The Frequencies report's Type filter also offers Quarterly, On Request and Annual Plan (see Frequencies).
Job History: Instance Name
Job History carries an Instance Name column and filter, reporting which named schedule instance the row's run belongs to.
| Column | Filter operators | Notes |
|---|---|---|
| Instance Name | Contains, Equals, Starts with, Is empty, Is not empty | The schedule instance the job ran under. Empty for a workflow that does not build named instances, so Is empty selects exactly the single-instance rows — and is how you exclude them. |
Workflow Name stays the bare workflow name in this report, not the composed
Workflow_Instance form the Processes grids show. That column is also the report's Workflow Name
filter, so a composed value copied out of a result and pasted back into the filter would match
nothing. The instance is reported in its own column instead.
Instance Name sorts like the other columns. Every Job History sort is applied over the fetched result, and a download is sorted the same way as the results page — see Job History downloads.
Job History: Agent Pool and Event Triggers
Job History also has an Agent Pool column and an Event Triggers column, and each is a filter as well.
| Column | Filter operators | Notes |
|---|---|---|
| Agent Pool | Contains, Equals, Starts with, Is empty, Is not empty | The agent pool or legacy agent group the job was assigned to. Empty for a job assigned to a single agent. |
| Event Triggers | Contains, Is empty, Is not empty | The events the job raises, each with the condition that raises it, separated by ; . Empty for a job that raises no events. |
Agent Pool shows the pool's current name. When that name cannot be looked up, the column shows the name the pool had when it was picked in the job editor, and when there is none, the pool's identifier. A filter matches the name the column shows, so a filter on a pool renamed since the job was saved can miss that job when its current name could not be looked up.
When pool names cannot be loaded right now, what happens depends on how the report uses the column:
| The report | What you see |
|---|---|
| Shows Agent Pool but neither filters nor sorts on it | The rows load, with the name saved on each job, under a warning, Some values may be out of date: Agent pool names could not be loaded. The Agent Pool column shows the name saved when each job was built. After a download, the same line appears under the download button. |
| Filters on Agent Pool with Contains, Equals or Starts with, or sorts on it | The report stops with Agent pool names are unavailable right now. Try again in a moment., because the rows or their order could be wrong. |
| Filters on Agent Pool only with Is empty or Is not empty | The rows load as usual. Those two operators need no names. |
Event Triggers names each event by its type, never by what it sends. Each entry reads as the condition, then the event type:
| The job's event | Reads |
|---|---|
| Raised when the job Failed | Job Status: Failed → $NOTIFY:EMAIL |
| Raised on an exit code greater than 5 | Exit Description: Greater Than 5 → $JOB:ADD |
| Raised on a completion expression | Completion Expression: <the expression> → <event type> |
| Raised on an LSAM feedback match | LSAM Feedback: <the match pattern> → <event type> |
An event's parameters — recipients, message text, job names — are left out, because they make the
cell long and can carry message bodies. An event whose type cannot be read shows
(custom event), and a condition saved without its value reads (no value) (or (no status) for a
job status). Because the filter matches the cell's text, Contains Failed finds jobs with
an event on failure and Contains $NOTIFY finds jobs that send a notification.
Both are read from the job instance: what it was built with, or what an edit to that instance in Processes has changed since.
Agent Pool and Event Triggers sort over the fetched result, and empty cells sort first.
Job History downloads
A Job History download is sorted the same way as the results page, for every sort rule and
every column you can sort on. To sort it, Reports reads every matching row first, so a sorted
download that would hold more than 100,000 rows is refused with This export is too large to sort by
<columns>. Narrow the filters, or remove the sort. A download with no sort rule is not read
first, and stops at 100,000 rows. Earlier builds sorted a download by its first sort rule only, and
some columns not at all.
Workflow History
Workflow History
Workflow History, under Operational Objects, lists one row per finished workflow instance, across any range of dates: each run that ended Completed or Cancelled. A run still in progress is not listed until it finishes. Where Job History answers what each job did, this answers how each workflow run went.
It needs an Environment and a Date filter, like Job History. Date is the workflow's schedule date and offers Between, On, Before and After.
| Column | Filter operators | Notes |
|---|---|---|
| Environment | Is | Required. The environment to report on. |
| Date | Between, On, Before, After | Required. The workflow's schedule date. |
| Workflow Name | Contains, Equals, Starts with | The bare workflow name. |
| Instance Name | Contains, Equals, Starts with, Is empty, Is not empty | The schedule instance the run belongs to. Empty for a workflow that does not build named instances. |
| Nested | Is (Yes / No) | Yes for a workflow that ran inside a container job. |
| Start Time / End Time | On, Before, After, Between | When the run actually started and ended. Empty for a run cancelled before it started. |
| Run Time | Equals, Greater than, Less than | End time less start time, shown as h:mm:ss. The filter takes a number of seconds. Empty for a run that never started, which a Run Time filter does not match. |
| Status | Is, Is not (Completed / Cancelled) | The run's final status. |
| Jobs | Equals, Greater than, Less than | How many jobs the run had. |
| Failed Jobs | Equals, Greater than, Less than | How many of them ended Failed, Marked Failed, Initialization Error or Missed Start Time. |
Every column except Environment sorts, and a download is sorted the same way as the results
page. A report that takes longer than 25 seconds to read stops with This report took too long to
run. Narrow the date range and run it again., as Job History does. A sorted download that would
hold more than 100,000 rows is refused with This export is too large to sort by <columns>. Narrow
the filters, or remove the sort.; one with no sort rule stops at 100,000 rows.
Each workflow instance is one row, showing how its latest run ended. A nested workflow inside a recurring or retried container job keeps the same instance, so only its latest run is listed. A workflow instance replaced by a rebuild is no longer listed, and an instance that is reopened leaves the report until it finishes again.
Workflow History lists only the workflows your roles let you see. To see one workflow's runs from Processes, use View Workflow History — see Earlier runs of a workflow.
Frequencies
Frequencies: run dates
The Frequencies report lists the dates each frequency produces: one row per frequency and Run Date, with Frequency Name, Type and Description beside it. Every frequency you can see in the Toolkit is listed, whether or not any job uses it; a deleted frequency is not. The Date Range filter (Between) sets the window — the next 30 days when you set none, and at most a year. Without a sort, rows come in Run Date order, then by frequency name.
The dates are the frequency's own pattern dates, the same ones the frequency dialog's forecast shows (see The dialog's forecast and the build). Monday to Friday are the working days and no holidays apply, so the dates do not reflect any workflow's calendars. The pattern's own calendars still apply:
| Calendar | Effect on the listed dates |
|---|---|
| An Annual Plan frequency's Plan calendar | Its dates are the run dates, moved by the plan's offset. On Master Holiday Calendar (system), the Master Holiday Calendar's dates are the run dates |
| A frequency's exclusion calendar | Its dates are left out |
An On Request frequency lists every day in the range, weekends included, as its forecast does.
The report has no Workflow Name column or filter. It reports frequencies, not workflows. A report saved with Workflow Name still opens and runs, without that column, filter or sort rule, and saving it again removes them for good. To see when a workflow will run, with its holiday calendars applied, use the workflow editor's Forecast view rather than this report.
Running the report needs permission to view frequencies; without it the whole report is refused.
Rows the report leaves out
A frequency whose dates cannot be worked out is left out, and a warning above the results, Some rows are not shown, names each one and why. The same frequencies are also left out of the download. After a download, a line under the download button says This file leaves out N frequencies. The list is on the page. An Excel download also carries a second sheet, Report notes, with a row for each left-out frequency under Frequency, Calendar and Reason — up to 50, as on the page, followed by And N more. when there are others. Calendar names the calendar the way the warning on the page does, exclusion calendar or plan calendar, and is blank when no calendar caused it. A CSV download carries the data columns only.
The report runs again for each download, so the file and the page can disagree if a calendar changed or could not be read in between. When the file leaves out a different number of frequencies than the page lists, the line under the button gives both counts — This file leaves out N frequencies, but the page lists M frequencies. The report runs again for each download. Reload the page to see the current list. Only the counts are compared.
| The warning reads | What happened |
|---|---|
| its plan calendar was deleted, so it has no plan dates. (or was not found) | An Annual Plan's calendar is gone. That frequency lists no dates. |
| its exclusion calendar was deleted. (or was not found) | The frequency is left out. |
| you do not have permission to view its exclusion calendar. (or plan calendar) | The frequency is left out. The report reads calendars as you. |
| its exclusion calendar could not be loaded just now. Try again in a moment. (or plan calendar) | The frequency is left out. Run the report again. |
| its run dates could not be worked out. | The frequency's run dates could not be worked out. The frequency is left out. |
| its saved pattern could not be read. Fix the frequency in the Toolkit. | The frequency's stored pattern is not valid — including one the frequency dialog's forecast would refuse, such as a weekly pattern with no day chosen — so retrying will not help. Fix the frequency in the Toolkit. The frequency is left out. Earlier builds listed run dates for some of these patterns that the forecast refused. |
The warning lists up to 50 entries, followed by And N more. when there are others, and scrolls when the list is long. The Frequency Name, Type and Description filters narrow the list the same way they narrow the results, and the count follows. A Date Range filter does not narrow it, because a left-out frequency has no dates to compare. A date range that ends before it starts, or names a date that does not exist, is refused rather than listing every frequency as left out.
Earlier builds read only a workflow-level frequency list that the editor cannot set, so the report was empty for every workflow built in the editor.
When the frequency list cannot be read, the report shows The frequency list is unavailable right now. Try again in a moment., on screen and for a download, rather than an internal error. When the list loads but every calendar the frequencies use cannot be read right now, the report shows The calendars these frequencies use are unavailable right now. Try again in a moment. instead of leaving out every frequency that uses one. When only some cannot be read, those frequencies are left out and named in the warning, as above.
Service Requests
Service Requests
A Service Requests report answers "what is published, who owns it, and how big is it" across every service request in the tenant. Every column is also a filter, and the same seven are offered in both roles.
| Column | Filter operators | Notes |
|---|---|---|
| Name | Contains, Equals, Starts with | The request's name. All three operators ignore case. |
| Tags | Contains | The request's tags, joined for display. |
| Inputs | Equals, Greater than, Less than | How many inputs the request asks the requester for. |
| Events | Equals, Greater than, Less than | How many events the request fires when it is submitted. |
| Version | Equals, Greater than, Less than | The request's current version number. |
| Workspace | Contains, Equals, Starts with | The workspace the request is assigned to. |
| Last Updated | On, Before, After, Between | When the request was last modified. |
Inputs and Events are counts, not lists — a request with no inputs reports 0. Use them to
find the requests worth reviewing: a request with many inputs is the one a requester is most likely
to get wrong, and a request with none runs on a single selection.
Filtering and sorting happen over the fetched result rather than being pushed to the server, except for Name (narrowed server-side first) and sorting by Name or Last Updated in an export. A very large tenant is better filtered down before sorting on Tags, Workspace, or one of the counts.
Audit History
Audit History
An Audit History report answers "who changed what, and when". It sits under the Governance & Access category. Each row of an update is one changed value, not one edit: saving a workflow with three settings changed produces three rows. A create or a delete starts with one summary row instead (see below). Choose a Category and, optionally, narrow it with the other filters. Every column is also a filter.
| Column | Filter operators | Notes |
|---|---|---|
| Category | Is — required | The kind of object that changed, or All Categories. The report will not run without one. |
| Name | Contains | The name of the object that changed. |
| Data Changed | Contains | The setting that changed. On a create's or a delete's summary row, the kind of record, such as Calendar Record or Workflow Record. |
| Action | Is | Create, Update, Delete, Enable, Disable or Status Change. |
| Changed By | Contains | A user's name or ID. A change the platform made itself reads System; search for System to find those. See Who an event's change is recorded under. |
| Changed At | On, Before, After, Between | When the change was made. The only column you can sort on. |
| Environment | Is | The environment the changed object belongs to. |
| Before Value / After Value | Contains | The setting's value before and after. A create's summary row has a blank Before Value and reads Record Added: <name> after; a delete's reads Record Deleted: <name> before and has a blank After Value. |
The Category list covers calendars, workflows, properties, thresholds, resources, frequencies, workflow deployments, scripts, script types, runners, tags, service requests, their categories and deployments, roles, workspaces, custom fields, agents, agent pools, connections, notifications, job instances, workflow instances, Job Execution Notes, legacy (LSAM) agent groups, runtime settings and z/OS JCL saves.
Things worth knowing before you run one:
- A create or a delete starts with one summary row. Creating a script named
Nightly-Cleanupgives one Create row with a blank Before Value andRecord Added: Nightly-Cleanupafter; deleting it gives one Delete row withRecord Deleted: Nightly-Cleanupbefore and a blank After Value. Data Changed on that row names the kind of record, Script Record here, so a Data Changed filter forScript Recordfinds it. To list what was added, filter After Value ContainsRecord Added; for what was removed, Before Value ContainsRecord Deleted. An update still gives one row per changed value. - Calendars, properties, thresholds, resources, agents, agent pools and roles also list their
values. Their summary row is followed by one row per value the record held: on a create,
Before Value reads
(Record Added)and After Value holds the value; on a delete, Before Value holds the value and After Value reads(Record Deleted). A calendar with many dates gives a row per date. The record's own name is not repeated as a row of its own. - An item added to or removed from a list is marked. When an update adds a job's event,
dependency, property or custom field, for example, Before Value reads
(Record Added); when it removes one, After Value reads(Record Deleted). A dependency's row names what it depends on, such as Dependencies Job-B, and a job's custom field is named by the field's name, such as Custom Fields Region. - Only changes someone made are recorded. Saving a workflow deployment or a service request deployment without changing it records nothing. A custom field default that Continuum fills in on a job when a workflow is saved is not recorded as a change by the person who saved it.
- A deployment's transformation rules are recorded on the deployment. Adding, changing or
deleting a rule on a workflow deployment or a service request deployment records an Update of
that deployment, under the person who made it. A rule's pattern and value are shown as
(hidden), or(hidden, changed)when they changed, because a rule can write a secret into the deployed configuration. - Reading it needs Audit History View, the same permission that governs the event log.
- A z/OS JCL save is recorded once it has an outcome. Each save from a z/OS job's
JCL dialog is an Update in the z/OS JCL category,
named
<agent> <DD name>(<member>), under the person who saved it. It records the save's details, such as the DD and member names, the z/OS user ID, the line count and the outcome:SAVED,REJECTED,NOT_APPLIEDorUNKNOWN. The JCL text itself is never recorded. - Changed By names the person. A z/OS JCL save and an OpCon MFT agent's API token reset are recorded after the request finishes, and they name the person by display name like every other change. A token reset recorded before this build still names the person by email address.
- A filter the report does not offer is refused, not ignored. So is a second Category filter. The message says what to remove, for example The Category filter can be used once. Remove the repeated Category filter.
- Secret values are never shown. A masked value reads
(hidden), or(hidden, changed)when it changed. You can filter on those words as shown. Changing an agent's API token, EASE password or local event token gives a row named API Token, Ease Password or Local Event Token, reading(hidden)before and(hidden, changed)after; the value itself is never recorded. Typing the same EASE password again records no change, while an API token you type in is always recorded as changed. Earlier builds recorded such a change as an update with nothing in it. Yes and No match a true or false setting, and dates and codes match the stored value, for example2026-11-02orFAILED_JOB. - Rows that only repeat another row are left out. An id beside the name it belongs to, or the environment of a record, is not listed again. A record whose only rows would repeat something keeps one.
- It shows the first 10,000 rows. The page says so and gives the total, as "more than 10,000" when it stopped counting. A download returns up to 100,000 rows; beyond that it is refused and asks you to narrow the filters, for example by adding a Changed At range.
- A slow report asks you to narrow it. If the history cannot be read in time, the message says so. If it is unavailable, including when it cannot be reached at all, the message asks you to try again later.
- Records stored before the report existed have no per-value rows until the platform rebuilds them.
In the same way, a create or delete recorded before the summary row was introduced still shows one
row per value, with
(Record Added)in Before Value or(Record Deleted)in After Value, until the platform rebuilds the report's rows. Rows recorded before this build take the record labels and the(Record Added)and(Record Deleted)markers when the rows are rebuilt; a job's custom field recorded before this build is still named by its ID, and rows already recorded for an unchanged deployment save or a filled-in default stay.
Who an event's change is recorded under
When a signed-in person sends an event, through a Self Service button or the events API, the change it makes is recorded under that person rather than System:
| Event | What is recorded under the sender |
|---|---|
$MACHINE:STATUS | The agent's operator-state change in Audit History, and the Set by the agent's status tooltip shows. See Taking an agent out of service. |
$JOB and $SCHEDULE events | The job or workflow change in Audit History, and the job's or workflow's own status history. |
An event raised by a job, a workflow, a notification, a Vision trigger or a legacy agent's MSGIN file still records its change as System: no person sent it.
Reports are not scheduled. Run an Audit History report whenever you need to show an examiner what changed, and download the result.
Roles
Roles
A Roles report answers "who can do what, and where" across every role in the tenant. It sits under its own Governance & Access category. Every column is also a filter, and the same eleven are offered in both roles.
| Column | Filter operators | Notes |
|---|---|---|
| Role Name | Contains, Equals, Starts with | The role's name. |
| Description | Contains, Equals, Starts with, Is empty, Is not empty | The role's description. |
| System Role | Is, Is not (Yes / No) | Built-in roles seeded by the platform. These cannot be edited or deleted. |
| Permission Count | Equals, Greater than, Less than | How many permissions the role grants. |
| Permissions | Contains only | The permissions the role grants, by name, such as Workflows: View, joined with ; . The filter also matches the permission IDs, as objectType.action, so a filter saved as workflows.view keeps finding the same roles. |
| Scope Count | Equals, Greater than, Less than | How many workspace/environment pairs the role applies to. |
| Scopes | Contains only | Where the role applies, as Workspace / Environment pairs. |
| Created At / Updated At | On, Before, After, Between | |
| Created By / Updated By | Contains, Equals, Starts with |
Five things about it are worth knowing before you build one:
Permissionscan be longer than what was picked in the role editor. Granting any action other than View also grants that object type's View permission (<Object>: Viewin this column), and the report lists what the role actually holds. A role showing more permissions than you configured is not a fault.Anyin a scope means unrestricted on that axis, not a missing value. A role scoped to one workspace and every environment readsPayroll / Any.PermissionsandScopesoffer Contains and nothing else. Both filters compare against the whole joined cell, so Equals would match only a role whose entire list is the search term, and Starts with only one whose alphabetically first entry is. They are deliberately left out rather than offered as traps.- The report describes what a role is configured to grant, which is now also what the services enforce — see Roles and permissions.
- Without Workspaces View, the Roles, Resources and Service Requests reports show workspace ids where they would show names, and filtering or sorting one on the workspace name is refused outright rather than quietly matching nothing. This applies to the report's export as well as the report on screen.
Only Role Name is narrowed server-side; everything else — including all sorting — is applied over the fetched result. Roles arrive in name order, so a report you have not sorted is alphabetical by name. Filter a very large tenant down before sorting on Permissions or Scopes, which are sorted on their joined text; Permissions sorts by the names it shows.
Tags
Tags: no References column
The Tags report lists Tag Name, Description, Created At and Updated At. It has no References column or filter: counting every tag's uses at once was the one report query that had to read every workflow, and it was removed. To see which jobs carry a tag, use the tag's Cross Reference view in the Toolkit — see Tags.
A Tags report saved with References still opens and runs, without that column, filter or sort rule. Its download keeps an empty References column until you save the report again.
When the tag list cannot be read, the report shows The tag list is unavailable right now. Try again in a moment., on screen and for a download, rather than an internal error.
Building a Report
Each report supports columns (selected and ordered), sort rules, and filters. In the builder, Choose Filters and Choose Columns set the filters and columns, and Order Filters & Columns opens a dialog with two parts: Sort Rules, where Add New Sort Rule adds up to five, each on a selected column, and Column Order, where you drag columns into the order the results and download use. Save in the dialog keeps the arrangement for the report you are building. Filter types:
| Filter type | Operators |
|---|---|
| Text | Contains, Equals, Starts with, Is empty, Is not empty |
| Number | Equals, Greater than, Less than |
| Single-select | Is, Is not; Job History's Job Termination Status also offers Is any of and Is none of, which take a list |
| Date/time | On, Before, After, Between |
For example, Job History offers filters for environment (required), date (required), start and end time, workflow/job/agent name, termination status, exit code, and run time. A filter with only one operator, such as Environment (Is), shows that operator as text rather than as a list to pick from.
The workflow, job and agent name filters take a * wildcard, the same way the
Processes page's do: payroll* is starts-with,
*payroll is ends-with, and a value with no * still matches anywhere in the name. ?, _ and %
are all literal.
The Scripts report's Type filter follows a renamed script type. The filter stores the script
type itself, not its name, so a saved report keeps returning the same scripts after the type is
renamed. A report saved by an earlier build, which stored the name, still runs by that name; open
it in the builder and the matching type is selected, so the next Save Changes stores it the new
way. A stored name that no longer matches any type is shown as <name> (not found). Earlier
builds stored the name only, so renaming a script type emptied every report filtered on it.
What a date filter matches
A date filter's controls take a date, while the values being matched are full timestamps. A date therefore means the whole UTC day it names — UTC because the report grid renders and labels its date columns in UTC, so the filter agrees with what you can see.
| Operator | Matches |
|---|---|
| On | Anywhere within the named day. |
| Between | From the start of the from day through the end of the to day — inclusive at both ends. |
| Before | Strictly earlier than the named day. The day itself is excluded. |
| After | Strictly later than the named day. The day itself is excluded. |
On, Before and After against one date therefore partition the timeline: a row satisfies exactly one of the three.
On matched nothing at all — only a row stamped at exactly midnight could satisfy it — and Between dropped every row on the to day after midnight, which made "created today" inexpressible. Neither reported an error; the result set was simply short or empty and looked legitimate. If you built a report around either quirk, re-check it.
After changed too, and deliberately: it used to return rows from the named day itself and now excludes them. A saved report using After will return fewer rows than it did — use On as well if you meant to include the day.
Is empty and Is not empty
A text value can be blank in two ways — stored as an empty string, or never set at all — and the two are indistinguishable on screen. Is empty matches both, and Is not empty excludes both.
The Jobs report's Documentation filter and the Scripts and Roles reports' Description filters matched only the never-set form. Because almost every job created through the editor stores an empty string instead, Is empty returned close to nothing in an environment full of blank documentation, and Is not empty returned everything including the blanks. Both grid and export were affected, and both are now correct.
One related change: on those three filters, Contains or Equals with an empty value now matches every blank row rather than only the never-set ones. Contains and Equals with a real value are unaffected.
Column order and column selection stay in step. Checking a column adds it to the end of the column order, whether or not you open Order Filters & Columns. Earlier builds only recorded the order when that dialog was used, so a column you had checked could be missing from the order — and because results and exports follow the order, the column then appeared in neither. A report already saved in that state repairs itself when you open it: any checked column missing from the stored order is appended, so it renders and exports from then on.
Saved Reports and Export
Saved reports, results, and export
- A report can be saved (name, description, columns, column order, sort rules, filters) and re-run later. Saved reports are shared: everyone in your organization who can open Reports sees the same list, and each name can be used only once (ignoring case). Renaming a report by changing only the letter case of its own name is allowed.
- A report runs once it is saved: Create Report (or Save Changes when you are editing one) returns you to the Reports page, and each saved report's actions menu offers View (run it and show the results), Edit, Copy (a new report with the same filters and columns, under a name you choose) and Delete. Download Report on the results offers CSV and Excel (.xlsx).
- A name already in use is reported on the field as you type it — A report with this name already exists. — and Create Report stays unavailable until you change it. When two people save reports under the same name at the same moment, the first save wins and the second is refused with the same message on the field.
- Saving, changing and deleting a saved report are checked against your roles: they need Reports Create, Reports Edit and Reports Delete. See Environments and saved searches.
- The Reports page lists every saved report, grouped by report type and then object type, with no page limit. Earlier builds showed only the first 20 in name order and gave no indication the rest existed.
- Results are paginated (25 rows per page by default), with a truncation warning for large sets;
large exports stream, in both formats.
- While the next page loads, the current rows stay on screen, dimmed, and are announced to screen readers as busy.
- If a page fails to load, the pager stays, so you can go back to a page that worked. Only a report whose first page fails shows no pager.
- Opening a different report starts it on page 1. The page size you chose is kept.
- Result columns can be resized. Drag the edge of a column header to make it wider or narrower. Each report keeps its own widths, in your browser — see Resizing table columns.
- An open report does not refresh on its own. Switching to another browser tab and back leaves the results as they were; open the report again, or change page, to fetch them.
- Export formats: CSV and Excel (
xlsx). An Excel download is written as its rows arrive, so a large one finishes rather than running out of memory. Its header row is bold, and its column widths are set from the header and the first 200 rows. - A download can be cancelled. While one runs, the button reads Downloading… with a Cancel beside it. Cancel stops the download and saves no file; closing the tab does the same.
- An export that fails part-way saves no file. The download stops and the page says The export did not finish, so no file was saved. Run the export again. Earlier builds could save a CSV that had been cut off part-way as though it were complete.
- Reports count against a usage allowance per signed-in user. Viewing a page of results, moving to another page and exporting each fetch the report's rows, and a large report fetches them in many requests. The allowance is counted for each person separately, so one person's large reports no longer use up everyone else's.
- A Jobs report reads one page at a time. Each page you view is read already filtered and sorted, and a download reads its rows in batches of 1,000 in the report's sort order — see Jobs: large tenants.
- A report the platform cannot produce right now says so once. Its message appears straight away and the report is not fetched again behind the scenes, so one report that cannot load does not hold up your other reports and searches. Run it again when you are ready. Earlier builds kept retrying such a report, which could leave every report and search page waiting for up to 30 seconds.
- A report whose list cannot be read right now says which list, and to try again. The Jobs, Calendars, Frequencies, Properties, Resources, Scripts, Service Requests, Tags and Thresholds reports each name their own list — for example The job list is unavailable right now. Try again in a moment. — on screen and for a download. Running such a report again and again does not make your other reports and searches fail while that list is unavailable.
- A filter the report type no longer offers is dropped, and the report says so. The results page and the builder name the removed filters and warn that the report now shows rows they used to leave out; edit and save the report to keep it that way, or change its filters. In the builder the warning shows while the report's own object type is selected. An Audit History report refuses such a filter instead of dropping it — see Audit History.
- A column the report type no longer offers is left out of the results and the download alike. Earlier builds put it in the download as an empty column. If none of a report's columns are left, Copy says The copy has no columns: the copy is saved without columns, so edit it and choose its columns before you view it.
- Every filter is checked when you save. While a filter is turned on with no value, or a value it cannot use, Save is refused with Some filters are incomplete or invalid. Fix them or turn them off to save. and each such filter shows its problem. That includes required filters, such as Job History's Environment and Date, so a report that could never run cannot be saved. A report saved through the API is checked too: a filter or operator the report does not offer, a value of the wrong kind, a choice that is not one of the filter's fixed options, a day that does not exist such as 30 February, and a Date Range whose start is after its end are all refused. A filter saved earlier is not re-checked until you change it, but copying a report checks every filter it carries.
- Reports are read-only — they don't change anything.
- The Agents report's Type filter lists every agent type by the name the Agents page
shows — Universal, Windows, SAP R/3 and CRM and so on — and narrows the report with
Is or Is not. The Type column itself shows the stored value, such as
IBM_iorSAP_R3. - Reports run on demand. There is no scheduled or emailed delivery of a report or of a saved search; run it and export the result when you need it.