Issuer Health Runs Help and Documentation

Learn how to use the System Health page to confirm whether issuer-health run processing is healthy, review completed and failed runs, inspect processing totals, understand run modes, and move to detailed runs, alerts, monitoring, or the main dashboard.

System Health Overview

The Issuer Health Runs Health page is a thin operational summary of live issuer-health run-history data.

Use it to confirm:

  • Whether the subsystem is currently healthy.
  • How many runs have completed or failed.
  • Which processing mode created the runs.
  • How many rows were available and processed.
  • Whether the run watermark advanced.
  • How many platform events were generated.

Shortcut Links

View Runs

View Runs opens the detailed issuer-health run history. Use it when you need individual run records rather than the summary shown here.

View Alerts

View Alerts opens issuer-health alerts generated from processed evidence.

View Dashboard

View Dashboard opens the main operator dashboard.

View Monitor

View Monitor opens the Issuer Monitoring Console.

Health Status

The Health card summarizes the overall state of issuer-health run processing.

Healthy The displayed run history does not currently indicate a failed or unhealthy processing state.
Healthy does not mean every downstream metric is populated It means the run subsystem completed without the health conditions represented by this summary. Separate monitoring or recovery pages may still show incomplete evidence.

Run Summary Cards

RunsTotal issuer-health runs represented.
CompletedRuns that finished successfully.
FailedRuns that did not complete successfully.
Dry RunsRuns executed without committing normal production effects.
Latest StartStart time of the newest run.
Latest EndEnd time of the newest run.
Latest StatusLifecycle state of the newest run.

Processing Totals

Total RowsTotal source rows available to the run.
Total ProcessedRows or grouped signals actually processed by the issuer-health pathway.
Platform EventsOperational events generated from the run.
Total Rows and Total Processed can differ In this example, 10,000 source rows produced 25 processed issuer-health signals. Processing may aggregate many source rows into a smaller number of issuer-level events.

Watermark Advanced

The watermark indicates whether the processing boundary moved forward during the run.

A value of 0 means the run did not record a watermark advance.

Zero does not automatically mean failure A run can complete successfully without advancing the watermark if it processed a synchronization mode, repeated evidence, or a pathway that does not use that watermark.

Status Counts

This table groups runs by lifecycle status.

KeyThe status name, such as completed or failed.
CountThe number of runs in that status.

The supplied page shows one completed run.

Mode Counts

This table groups runs by execution mode.

KeyThe run-mode identifier.
CountThe number of runs using that mode.

csv_job_signal_sync

This mode indicates that issuer-health signals were synchronized from a completed CSV investigation job.

How to Interpret the Supplied Page

The displayed values indicate:

  • One issuer-health run exists.
  • The run completed successfully.
  • No failed or dry runs are recorded.
  • The run was created through CSV job signal synchronization.
  • 10,000 input rows produced 25 processed signals and 25 platform events.
  • The subsystem reports Healthy.
Operational reading The issuer-health bridge executed successfully and produced issuer-level event output from the uploaded CSV investigation.

Recommended System Health Workflow

  1. Confirm that Health is Healthy.
  2. Review Completed and Failed counts.
  3. Check Latest Start, Latest End, and Latest Status.
  4. Compare Total Rows with Total Processed.
  5. Review Platform Events.
  6. Check Watermark Advanced in context.
  7. Review Status Counts and Mode Counts.
  8. Select View Runs for individual run details.
  9. Select View Alerts to confirm downstream alert generation.
  10. Select View Monitor to review issuer-level monitoring output.
Do not certify the entire platform from this page alone This page summarizes issuer-health run processing. Use Dashboard, Monitor, Recovery, Network, and Runtime Pathway Certification for broader production-readiness review.