Skip to main content

Reports

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

  1. Open Reports and select New Report.
  2. Enter a Report Name, and pick a Report Type and Object.
  3. Choose filters and columns, and set the sort order.
  4. Save it, run it, and export the results if you need them. The full walkthrough is Create and run reports.
Notes
  • 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> or Record 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.
Watch out
  • 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.