Operator Dashboard Help and Documentation

Learn how to use the Issuer Supervisor Operational Dashboard to identify urgent issuer conditions, search operational rows, open investigations, review timelines and replays, inspect full records, and follow escalation guidance.

Dashboard Overview

The Issuer Supervisor Operational Dashboard combines alerts, processor tasks, investigation links, and escalation guidance in one operational workspace.

Use this page to answer questions such as:

  • Are any issuer incidents critical right now?
  • Which issuers require immediate investigation?
  • How many tasks remain open or unresolved?
  • Which queue should receive each issue?
  • What evidence and historical context are available?

Status Banner and Live Monitoring

Critical issuer incidents detected

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

  • Red: one or more critical conditions require prompt attention.
  • Yellow: warnings exist, but no current critical condition dominates.
  • Green: no urgent condition is represented.

Live Monitoring Active

The pulsing green dot indicates that the dashboard's live refresh behavior is active. The “Last refreshed” value counts the time since the displayed dashboard content was loaded.

The live indicator is not a resolution signal A green heartbeat means the page is actively monitoring. It does not mean the issuer conditions themselves are healthy.

Summary Cards

AlertsTotal alert rows represented on the dashboard.
Queue ItemsTotal processor action tasks currently represented.
IssuersDistinct issuer BINs involved in current dashboard activity.
CriticalNumber of critical conditions.
WarningsNumber of warning-level conditions.
Escalations NeededItems that require escalation guidance or routing.
High EscalationsHighest-priority escalation items.
LatestTimestamp of the newest represented event.
Cards are summaries, not buttons They provide a quick operational count. Use the tables below to inspect and act on individual rows.

Processor Action Queue

This table is the main operational worklist. Each row represents an issuer signal that has been routed for escalation, triage, or follow-up.

Critical rows generally appear with red badges and should be reviewed before warning rows, subject to your organization's operating procedures.

Processor Action Queue Columns

Created AtWhen the task was created.
SeverityThe seriousness of the detected signal.
QueueThe operational queue receiving the task.
PriorityThe urgency assigned to the work item.
OwnerThe owning team or role; “Unowned” means no owner is recorded.
Priority ScoreA numeric ranking used to order work.
Issuer BINThe issuer cohort identifier.
MetricThe measurement that generated the task.
SummaryA plain-language description of the evidence.
Routing ReasonWhy Zahlen placed the task into its queue.
Task StatusWhether the task is open, in progress, or otherwise classified.
Assigned OperatorThe person currently assigned; “unassigned” means no operator is recorded.
Last Action AtWhen the most recent task action occurred; a dash means none is recorded.
Resolution StatusWhether the underlying issue is resolved.
ActionsLinks for examining evidence and continuing the workflow.
Initial-decline data can create zero-recovery signals A row showing 0 recovered events may come from an initial decline file before later retry outcomes are available. Read the summary, confidence, telemetry context, and investigation timeline together.

Row Action Buttons

Investigate Now

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

Use it when you are ready to begin reviewing the specific incident immediately.

Investigation

Investigation opens the same investigation context as a secondary navigation option.

Timeline

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

Use it to see the sequence of events and determine whether the signal is isolated, recurring, improving, or deteriorating.

Replay

Replay opens the replay view for the selected issuer and time window.

Use Replay to reconstruct how the system interpreted the evidence and reached its operational result.

Full Records

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

Use it when the summarized evidence is not sufficient and you need to inspect the underlying records.

Actions preserve context The links carry the issuer BIN, country, card brand, and relevant time window so the destination page opens the correct investigation context.

Recent System Events

This section shows recent operational events in chronological form. The timestamp indicates when each event occurred, followed by a description of what changed.

Use this section to understand recent dashboard activity before opening a specific queue item.

Alerts Table

The Alerts table presents issuer signals in a more concise alert-oriented format.

Created AtWhen the alert was created.
SeverityCritical, warning, or another alert level.
Issuer BINThe issuer cohort affected.
CountryThe issuer country.
BrandThe card brand.
MetricThe measurement that triggered the alert.
SummaryThe alert evidence in plain language.
ActionsInvestigation, timeline, replay, and record links.

Escalation Guidance

This table explains which issues need escalation and where they should be routed.

Created AtWhen the escalation guidance was created.
SeverityThe underlying issue severity.
Escalation LevelThe recommended urgency of escalation.
Target QueueThe destination queue for follow-up.
MetricThe triggering measurement.
Suggested ActionThe recommended next operational step.
ReasonsThe evidence supporting the recommendation.
ActionsLinks to supporting investigation views.
Guidance supports operator judgment Escalation guidance explains the recommended route, but operators should still review confidence, context, timeline, and full records before taking irreversible action.

Automatic Refresh and Progressive Row Loading

The Dashboard automatically requests refreshed page content approximately every 60 seconds.

  • Your current search text is preserved during refresh.
  • Your vertical scroll position is preserved.
  • The visible tables are reinitialized after refreshed content is loaded.

Progressive Row Loading

Without a search term, the page initially shows a batch of rows and reveals more as you scroll near the bottom. When a search term is active, all matching rows can be shown.

Refresh failure behavior If a background refresh fails, the current dashboard remains visible. The page does not discard the content already loaded in your browser.

Recommended Dashboard Workflow

  1. Read the status banner and confirm whether critical conditions exist.
  2. Review the summary cards for scope and workload.
  3. Search by issuer BIN, job ID, severity, or response code when narrowing the dashboard.
  4. Review the highest-priority Processor Action Queue rows first.
  5. Read the Summary and Routing Reason before opening an action.
  6. Select Investigate Now for the most urgent item.
  7. Use Timeline to understand sequence and persistence.
  8. Use Replay to reconstruct system interpretation.
  9. Use Full Records when row-level evidence is required.
  10. Review Alerts and Escalation Guidance for corroborating context.
  11. Assign, escalate, or resolve work according to approved operational procedures.
Do not act on severity alone Confirm the issuer identity, confidence, observation window, data stage, and supporting evidence before making processor or customer-impacting changes.