Scrydon
Platform

Platform Health

The Settings → Platform → Health page is a live status board for your Scrydon deployment — it checks that every service is reachable, that their dependencies are up, and that internal service-to-service authentication works.

Platform Health is a live status board for your Scrydon deployment. Open it from Settings → Platform → Health. It runs a battery of read-only checks and shows, at a glance, whether everything is working.

Platform Health is available to organization administrators. Every check is read-only — opening the page never changes any configuration or data.

What you see

  • Overall banner — a single verdict: All systems operational, Degraded, or Outage.
  • Checks table — one row per individual check, which you can search (type to filter) and sort. Each row shows what is being checked, a status, and a Context column with the detail (the error text, the address probed, and response time). The Type column groups the checks:
    • Reachability — is each Scrydon service responding? (OK · Degraded — answered but something is off · Unreachable — no response · Skipped — not configured in this environment).
    • Dependency — is each service's backing store (for example its database) up?
    • M2M — can Scrydon's internal services authenticate to one another? (OK is healthy; Denied means an internal permission is mis-configured.)
    • Migration — does each service's database have every update it expects? Pending migrations means an upgrade step was not run — the row lists exactly which database updates are missing, so your operations team knows what to apply. Each row can also be expanded to show which migrations have already run. (A common cause of problems after an upgrade is a forgotten migration step; this check makes it visible.)

Re-running the checks

The page checks everything when it opens. Press Re-run checks at any time to probe again — useful while you are bringing a deployment up or after changing configuration.

When something is red

A red result points your operations team at the failing service or dependency. Share what you see (which service, which status) with your administrator or Scrydon support — combined with the Download debug package option on the organization settings page, it gives a precise starting point for diagnosis.

On this page

On this page