System status

The status page (admin-only) reports your organization’s own job activity and the running arcodash version, nothing from other organizations, and nothing about workers outside your organization.

What it reports

The response has a top-level status and version, with the job counters nested under jobs:

{
  "status": "ok",
  "jobs": {
    "queued": 0,
    "in_flight": 0,
    "recent_success": 0,
    "recent_failure": 0,
    "recent_cancelled": 0
  },
  "version": "<the running build's version>"
}

Field	Meaning
status	Overall status string.
jobs.queued	Jobs waiting to run, queries, scheduled refreshes, monitor checks, and similar background work.
jobs.in_flight	Jobs a worker has picked up and is actively running right now.
jobs.recent_success	Jobs that finished successfully recently.
jobs.recent_failure	Jobs that failed recently.
jobs.recent_cancelled	Jobs cancelled recently.
version	The backend’s running version.

What to look for when queries feel slow

• queued climbing and staying high while in_flight stays flat, work is arriving faster than workers are draining it. This points at worker capacity, not a single bad query.
• queued high but in_flight also rising, the system is working through a backlog; give it a little longer before assuming something’s stuck.
• recent_failure elevated, something is failing outright rather than running slowly, check the specific query or monitor for an error, not general capacity.
• Everything near zero but a specific dashboard still feels slow, the bottleneck is more likely the query itself (or the database it’s running against) than arcodash’s job queue at all.

There’s no historical trend graph here, this is a live snapshot of right now. For a record of who changed what over time, see the audit log instead.

Where to go next

• Audit log, what happened, as opposed to what’s happening now.