Skip to content

Job Floor

Job Floor shows the health of scheduling and delivery: stalled environments, backlog, failure rate and failure classes, reports that keep failing, risky schedule owners and e-mail sent outside the company.

Image of the Job Floor page with all tiles, the When jobs run heatmap, Why jobs fail, Failed runs by destination, Outcomes over time and the grid

../../images/web-console/insights/jobs-full.png

What it answers

  • When did each environment last complete a scheduled job?
  • How many schedules are pending or paused, and which are overdue or set more than a year ahead?
  • What share of runs failed, and why (delivery, database, security, platform, report)?
  • Which reports failed their last three or more runs and are still scheduled?
  • Which live schedules belong to service, disabled or dormant accounts?
  • Which schedules e-mail addresses outside the company, and which addresses are malformed?

Open it

In the BusinessObjects console, select Insights > Job Floor.

Filters

Filter Values Effect
Environments one button per environment Limits every panel.
Window 1d, 7d, 30d, 90d, 180d, 365d (default 90) Defines which runs are counted. When the selected environments have no run in the window, all runs since data starts are used and the tiles say so.
People + service accounts / People only toggle Controls whether service accounts are counted.
Runs / Failures / Planned segmented control on the heatmap Switches the heatmap between completed runs, failed runs and upcoming scheduled runs.
Focus click a tile, heatmap cell, error class, destination or day Filters the Schedules and instances grid.

Panels

Panel What it shows Source
Days since last good run The environment that has gone longest without a successful job; the note lists every environment. Instances
Pending / paused schedules Pending and paused schedules, recurring and one-off; how many are overdue and how many next run more than a year away. Schedules
Failure rate Failed runs out of all runs in the window, the top error family and the top error class. Instances
Failing 3+ runs in a row Reports whose last three or more runs all failed, how many still have a live schedule, and the longest streak. Instances
Owner risk Live schedules owned by disabled users, users with no logon in 90 days, or service accounts. Schedules, user accounts
Email to external domains Documents e-mailed outside the company, still-scheduled count, addresses and domains, malformed addresses. Needs Internal mail domains: on the MMA Settings > Web Apps page; without it the tile says Not configured. Schedule destinations
Report probes Link to Reliability > Flight Recorder. Click a grid row to see that report's probe state. Flight Recorder
When jobs run Day-of-week by hour heatmap (hours in UTC). Instances, schedules
Why jobs fail Failed runs by error class, grouped into Delivery, Database, Security, Platform, Report and Other. Instance errors
Failed runs by destination Failed runs per destination: File system / share, FTP, SFTP, Email, BI platform (default), BI inbox, Google Drive, OneDrive, No explicit destination. Schedule destinations
Outcomes over time Runs per day by outcome. Instances
Schedules and instances Report, schedule or instance, kind, status, recurrence, owner, submitter, start and end, minutes, next run, failures in a row, error class and family, error text, destinations, external recipients, folder. All of the above

Image of the Job Floor tiles with the Failure rate tile selected

../../images/web-console/insights/jobs-tiles.png

Image of the When jobs run heatmap in Failures mode next to the Why jobs fail panel

../../images/web-console/insights/jobs-heatmap-errors.png

Image of the Schedules and instances grid filtered to Reports whose last 3+ runs all failed

../../images/web-console/insights/jobs-grid.png

Destination fix list

When you focus on a destination, the grid becomes a fix list with the instance id, schedule id, failure time or next run, status, destination, the account it logs on as, where it writes, owner, error or reason and folder. The ids let you find the object in the MetaMiner Client or in the CMC.

Export

Export the grid with Excel or CSV, or copy any panel's SQL. See Insights Dashboards.