Platform status

Platform status reports Data freshness, Transactions, Platform API, and Workflows health. Use its current signals, operational metrics, and history to identify the service that needs investigation. The page is read-only.

Check this page first when something elsewhere in the Console looks wrong and you need to know whether the platform itself is degraded before troubleshooting further. It never surfaces an organisation-specific problem, only platform-wide service health.

For a SettleMint-hosted environment, the public SettleMint status page reports platform-wide availability and incident history outside the Console. Use this page for this deployment's telemetry; use the status page when you need SettleMint's published service status. The SettleMint Trust Center carries the security and compliance documentation an audit review needs.

Each of the four areas answers a different question, and knowing which one to open saves time.

The Platform HealthPlatform Health lets a platform admin see in one glance whether the platform is healthy right now, instead of checking a dozen dashboards.Read the concept summary uses the worst verdict across the four areas. One degraded area makes the summary amber, even if the others are healthy.

The four verdicts rank from lowest to highest, and the header shows the highest rank among the areas that answered:

An area that answered contributes its verdict to that ranking. An area that reads No data yet, or whose query failed, contributes no verdict, but it is never read as healthy: "All systems operational" appears only when every area answered with a measured verdict. When the measured areas are all operational and at least one area has nothing to report, the header reads "Partially reporting" in grey instead, and a line under it names the areas with no data. A degraded or outage verdict elsewhere still shows its own colour and label, with the same line naming the silent areas beneath it. A failed query also shows the Retry button.

Above the four areas, the row labelled "Operational metrics" reports five numbers, though only three cover the full day. Each card has the same five lines: the title, the figure with its unit, a change line, a 24-hour trend, and a helper line. The change line reads "vs prior 24h" and its arrow follows the direction of the number; its colour says whether that direction is good, so a rising completion time is red and a rising completion count is green. Each card and its trend use the colour of the relevant health area. The three workflow cards use Workflows. Data delay uses Data freshness. Blocks indexed has no area verdict and stays uncoloured.

A card with nothing to measure yet keeps its shape and says what will fill it. A card the page could not load reads "Unavailable", and a Retry button under the row re-runs its query; that state means the page could not reach the platform, not that the platform has no data.

The three aggregates describe volume and throughput, and they can look strong even while an area below reports degraded: completing high work volume slowly, rather than not at all, is exactly what a degraded verdict describes, not an outage. Below the four areas, a History grid draws the platform's worst severity for every UTC hour of the completed days in a rolling window: one column per day, oldest first, and one row per hour. A short outage colours only the hours it lasted, and an hour never reads worse than its day. Hover a cell to see its date, UTC hour range, and verdict. Use the grid to tell a brief incident from one that ran all day, and whether today's signal is a one-off blip or part of a trend that has been building.

When Data freshness or Platform API needs the extra role you do not hold, its tile stops being clickable. It still shows its title, verdict badge, consequence line, sparkline, and footer stats, so work from those instead.

StepsCopy Anchor Link

TroubleshootingCopy Anchor Link

Platform status is not in the sidebar

Ask an administrator for the Admin or System Manager role.

A signal looks stale

No query on this page polls on its own. Each area and the metrics row cache their read for 30 seconds. That number is a floor on how soon a refetch reaches the network once something triggers one, not a promise that the page refreshes by itself. Reload the page to force a fresh read. The "Updated" timestamp redraws its relative wording only once a minute, even while the page sits open and idle. Between redraws it can under-report the data's actual age by up to a minute, looking fresher than it is rather than staler.

Data freshness says indexer telemetry is not arriving

At least one chain registered for indexer health has no current sample. A sample older than three of its own collector ticks no longer counts as current, so the area stops showing the last verdict it saw and reads No data instead, even when the other chains are healthy. This is a fault in the health collector, not proof that the indexer is healthy or down: check whether indexed data elsewhere in the Console is current, and treat it as a monitoring outage until samples return.

Data freshness shows chains out of sync

The verdict comes from each chain's latest indexer sample, and the tile's first line names the reason. Degraded means the indexer is 10 or more blocks behind the chain tip, is ahead of the tip it was checked against, or has indexed no new block for 5 minutes while blocks wait. Outage means it is more than 100 blocks behind, or has indexed no new block for 15 minutes while blocks wait. An indexer at the chain tip is in sync, however long the chain has gone without a new block; a chain that stops producing blocks shows under Transactions. While a chain is out of sync, anything reading indexed data (balances, transaction history, feed values) reflects an older state than what is on-chain. Open the data freshness detail view to see the current delay and recent sync error count before assuming a specific balance or history view elsewhere in the Console is wrong.

Workflows shows a stalled count above zero

A stalled workflow is background work that started in the last 24 hours but has not progressed, distinct from one that failed outright. The count covers the same day as the completed count it is compared with, so a status row left running long ago cannot keep the area in outage. Open the workflows detail view to see which one is stuck; it still lists older runs that never finished. A growing stalled count or work that exceeds its expected processing time requires investigation.

The header reads Status unavailable instead of a verdict

This means none of the four areas answered the page's own query, a failed page load, not a platform verdict; a real degraded or outage state still shows its own colour and label instead. Retry re-runs the four area queries and remounts the metrics row, the four area tiles, and the history grid below them. If Retry keeps failing, check your own connection or session before assuming the platform is down.

An area reads No data yet

The area has no current telemetry: either it has not produced any yet, most often right after it first comes online, or its collector stopped. It never outranks a real degraded or outage state sitting elsewhere, and it never lets the header read "All systems operational"; the header names it under the verdict instead. If it does not clear after a normal refresh, treat it the same as a stale signal, above.

Frequently asked questionsCopy Anchor Link