Issuer Supervisor Operational Dashboard Help and Documentation

Learn how supervisors use this page to monitor ownership, escalation pressure, aging work, alerts, queue status, recent system events, and operator guidance across issuer operations.

Supervisor Dashboard Overview

The Issuer Supervisor Operational Dashboard provides a supervisory view across queue ownership, escalation pressure, alerts, unresolved work, and recommended actions.

Use it to:

  • Identify critical issuer conditions.
  • See whether queue items are owned or unassigned.
  • Review priority and aging pressure.
  • Compare alerts with routed work.
  • Review escalation recommendations.
  • Open the evidence needed to guide operators.

Status Banner and Live Monitoring

The status banner summarizes the most serious current condition on the dashboard.

Critical issuer incidents detected

A red banner means at least one critical issuer condition is present and should receive prompt supervisory attention.

Live Monitoring Active

The pulsing green indicator confirms that the dashboard's live refresh behavior is active. “Last refreshed” shows how recently the current content was loaded.

Green means the page is active It does not mean the queue or issuer environment is healthy.

Summary Cards

AlertsTotal alert rows represented.
Queue ItemsTotal operational work items.
IssuersDistinct issuer BINs involved.
CriticalCritical conditions requiring urgent review.
WarningsWarning-level conditions.
Escalations NeededItems requiring escalation or routing.
High EscalationsHighest-priority escalation items.
LatestTimestamp of the newest represented event.
Summary cards do not open records Use the tables below to inspect and act on individual items.

Processor Action Queue

This table is the main supervisory worklist. It shows which tasks exist, how urgent they are, whether they are owned, and whether they remain unresolved.

Unowned critical work requires attention A critical row marked Unowned and unassigned should be reviewed for assignment or escalation according to your operating process.

Processor Action Queue Columns

Created AtWhen the task entered the queue.
SeverityThe seriousness of the issuer condition.
QueueThe workstream receiving the item.
PriorityThe operational urgency label.
OwnerThe owning team or role; Unowned means none is recorded.
Priority ScoreA numeric ordering signal.
Issuer BINThe issuer cohort identifier.
MetricThe measurement that generated the item.
SummaryThe evidence in plain language.
Routing ReasonWhy Zahlen placed the item in its queue.
Task StatusThe current work lifecycle state.
Assigned OperatorThe operator currently assigned.
Last Action AtWhen the most recent task action occurred.
Resolution StatusWhether the underlying issue is resolved.
ActionsLinks to evidence and investigation views.

Row Action Links

Investigate Now

Investigate Now is the primary action. It opens the issuer investigation page with BIN, country, card brand, and time window already supplied.

Investigation

Investigation opens the same investigation context as a secondary link.

Timeline

Timeline opens the issuer-health timeline for the same BIN and observation window.

Replay

Replay reconstructs how the evidence was interpreted.

Full Records

Full Records opens the row-level records from the originating investigation run.

Use the least summarized evidence needed Start with Investigation, then use Timeline and Replay. Open Full Records when the summarized evidence is not enough for a supervisory decision.

Recent System Events

This section lists recent operational events in time order.

Use it to understand what changed most recently before deciding whether an alert or queue item reflects a new event, a repeated signal, or an ongoing condition.

Alerts Table

The Alerts table gives a concise view of issuer signals before or alongside queue routing.

Created AtWhen the alert was created.
SeverityThe alert level.
Issuer BINThe affected issuer cohort.
CountryThe issuer-country context.
BrandThe card brand.
MetricThe triggering measurement.
SummaryThe alert evidence.
ActionsInvestigation, timeline, replay, and record links.

Escalation Guidance

This table explains which items should be escalated, where they should be routed, and why.

Created AtWhen guidance was generated.
SeverityThe underlying issue severity.
Escalation LevelThe recommended urgency.
Target QueueThe suggested destination queue.
MetricThe signal driving the guidance.
Suggested ActionThe recommended next step.
ReasonsThe evidence supporting the recommendation.
ActionsLinks to supporting views.
Guidance supports supervisory judgment Review confidence, telemetry context, timeline, and full records before directing irreversible operational action.

Automatic Refresh and Row Loading

The page automatically refreshes its content at regular intervals.

  • The current search text is preserved.
  • The current scroll position is preserved.
  • The tables are reinitialized after refreshed content is loaded.

Large tables may initially show a subset of rows and reveal more as you scroll. With an active search, matching rows are shown without relying on the normal batch limit.

Refresh failure is non-destructive If a background refresh fails, the currently displayed dashboard remains visible.

Recommended Supervisor Workflow

  1. Read the status banner and critical count.
  2. Review Escalations Needed and High Escalations.
  3. Search for unowned, unassigned, open, or unresolved work.
  4. Review the highest Priority Score items first.
  5. Read Summary and Routing Reason.
  6. Open Investigate Now for the most urgent item.
  7. Use Timeline and Replay to validate the interpretation.
  8. Use Full Records when detailed evidence is required.
  9. Compare the queue item with the Alerts table.
  10. Review Escalation Guidance before assigning or rerouting work.
  11. Confirm ownership and follow through until resolution status is updated.
Do not supervise from counts alone Counts indicate workload, but evidence, confidence, time window, and data stage determine whether escalation is justified.