Dashboards
- Synopsis
- Full Details
In briefContinuum opens on one of three read-only dashboards — Admin, Operator and Business User — each a set of widgets summarising state from other areas. It opens on the one you last viewed; on your first visit, that is Admin. The choice is yours, not your role's.
WhereDashboard at the top of the navigation. The dashboard selector at the top of the page switches between the three; Refresh all widgets and Pause auto-refresh are beside the Updated time.
When
- Admin: you are keeping the environment healthy — environment health, agents, relays, agent-pool utilization.
- Operator: you are watching the daily run — failed jobs, events, status counts, the agent-pool job queue. The Failed Jobs card lists failures in open workflows only, one table per environment.
- Business User: you submit service requests and want to see your own requests and events.
To act on what a widget shows, go to the area it summarises, such as Processes or Agents.
How
- Open Dashboard, and pick a dashboard from the selector.
- Read the widgets; they update by themselves over a live connection.
- If a warning beside the Updated time says live updates are paused or interrupted, the dashboard retries by itself; select Refresh all widgets to fetch the figures now.
- My Events shows only your own events, for the environment the dashboard is showing; an empty list means you have raised none.
- The Agents widget counts an agent marked out of service as Marked Offline or Marked Draining, not Online.
- The Agents widget lists up to 500 agents, and the Relays and agent-pool widgets up to 200 rows. A longer list carries a note, The list includes N of M …; the counts still cover them all.
- Event Summary and My Service Requests cover every environment of the types the Environment Filter selects, degraded and inactive ones included.
- While Pause auto-refresh is on, the widgets do not update until you resume.
- When too many dashboards are open across your organization, a newly opened one shows Live updates paused and waits for room; close dashboards you are not using.
Orientation is in Getting started.
OpCon Continuum opens on a dashboard. There are three, each built for a different kind of user, and you switch between them with the dashboard selector at the top of the page. Continuum remembers the one you last viewed and opens on it next time; on your first visit it opens on the Admin dashboard. The choice is yours, not your role's.
The three dashboards
| Dashboard | For | Typical widgets |
|---|---|---|
| Admin | Keeping the environment healthy | Environment health, agents, relays, agent-pool utilization |
| Operator | Watching the daily run | Failed jobs, event summary, workflow/job status counts, agent-pool job queue |
| Business User | Non-technical users | My Service Requests (your own requests), My Events |
The Business User dashboard's My Events widget shows your own events — the requests and actions recorded against your signed-in identity, scoped to the environment the dashboard is showing. Earlier builds showed the same five sample events, attributed to the same name, to everyone; that's fixed. The widget requires a signed-in identity, so it reports an error rather than falling back to everyone's events if it can't tell who is asking.
The Admin dashboard's Environment Health widget lists each environment's services, each with a coloured dot: green for Healthy, red for Unhealthy and grey for Unknown. Earlier builds showed an unhealthy service with the grey dot.
The Admin dashboard's Agents widget counts agents by the status you would read off an agent list, which combines observed connectivity with any operator mark. An agent marked out of service is counted as Marked Offline or Marked Draining rather than as Online, and selecting that slice lists exactly those agents. Agent-pool utilization follows the same rule: a pool's online figure counts only the agents that can actually take work.
A long list is capped, and says so. The Agents widget holds up to 500 agents, and the Relays, Agent Pool Utilization and Agent Pool Job Queue widgets up to 200 relays or agent pools. Past that, a note under the list says how much of it the widget holds, for example The list includes 500 of 812 agents. The Agents list is also cut short when its agents' names are long enough to make it too large to send, and the note says so in the same way. The counts and the chart still cover every agent or relay; only the list is cut. Earlier builds let a list of many long names grow too large to send, and the Agents widget then stopped updating. With a status selected, the note compares the agents or relays listed with that status's count. The full lists are under Agents, on its Agents, Agent Pools and Relays tabs.
The Operator dashboard's Failed Jobs card lists the failed jobs in open workflows — those not yet completed or cancelled — which is the same set the Failed tile on Job Status Counts counts, and both are counted from the jobs themselves, so the two numbers agree. A failure in a workflow that has since completed is no longer listed. Each environment in view has its own table, with its own count, paging and a page-size choice of 5, 10, 20 or 50 rows that your browser remembers; with one environment it is a single table. Each row shows the Job, Workflow, Status, Schedule date and End time, and selecting a column heading sorts by it. By default the newest end time comes first, and a failure with no end time is sorted last.
The Environment Filter at the top of the dashboard picks environment types. The Operator dashboard's Event Summary and the Business User dashboard's My Service Requests count every environment of the types you select, including Degraded and Inactive environments that the environment selector does not list. With every type selected and more than one environment, they cover your whole organization. Earlier builds counted only active environments on Event Summary, and My Service Requests followed the filter only when it came down to exactly one environment, showing every environment's requests otherwise.
- A selection that covers more than 100 environments uses the first 100 and shows Too Many Environments Selected, with how many were left out. Select fewer types to include them.
- An Event Summary tile opens the Event Log only when its counts cover exactly one environment, and one you can switch to. Otherwise its count cannot be selected, and hovering it shows Select a single environment to view results.
On Job Status Counts, selecting Failed scrolls to the Failed Jobs card. Selecting On Hold, Waiting or Running opens Processes filtered to that status across every schedule date, not only today's.
Under its count, a Job Status Counts tile can carry one more figure: Failed shows how many jobs had a start error (2 start errors), Waiting how many are late to start, and Running how many are late to finish. On Hold shows its count only. Earlier builds repeated the Failed tile's start errors under On Hold.
Every Job Status Counts tile, Running included, counts jobs in open workflows only, from the jobs themselves. A job still marked running in a workflow that has completed, been cancelled or been deleted is not counted. Earlier builds counted the Running tile from a separate source that included those workflows.
- The dashboards are read-only summaries — they surface state from other areas (Processes, Agents, Events, Self Service); they don't change anything.
- Which dashboard a user lands on follows their own last choice, so two users may see different home screens — that's expected.
- My Events is per-user, so two people looking at the same dashboard see different lists. An empty list means you haven't raised anything, not that the widget is broken.
- The widgets update by themselves, over a live connection the browser holds open — the Operator dashboard's Event Summary and the Business User dashboard's My Service Requests included, which earlier builds updated only when you reloaded the page or came back to its tab. It is reconnected automatically as your session refreshes its credentials. Earlier builds kept the original connection open past that point, and the widgets quietly stopped updating on a dashboard left open, while still showing figures that looked current. Reloading the page was the only way to notice. That is fixed; if a dashboard does look stale now, reloading is still the quickest check.
- The Updated time shows when the widgets last changed. It is set each time live data arrives and each time you select Refresh all widgets. If the time stops moving on a dashboard you are watching, select Refresh all widgets or reload the page. While Pause auto-refresh is on, the widgets do not update until you resume.
When live updates stop
When the dashboard cannot hold its live connection, a warning beside the Updated time says so, and the dashboard keeps trying on its own:
| The warning | What it means | Next try |
|---|---|---|
| Live updates paused: too many dashboards are open in your organization. Retrying automatically. | Your organization has as many dashboards open at once as the platform allows. Dashboards already open keep updating. | After 60 seconds |
| Live updates paused: too many requests. Retrying automatically. | Too many requests have come from you in a short time. | After 60 seconds |
| Live updates interrupted. Reconnecting… | The connection failed. | After 5 seconds |
The warning goes away as soon as live data arrives again. While it shows, the widgets keep their last figures; Refresh all widgets still fetches each one once. Closing dashboards you are not using, in any browser tab, frees room for the others. No warning shows while Pause auto-refresh is on.
Related topics