Skip to content

Audit & support

Flow run detail

Single-run forensics: status, throughput, students analyzed, errors, and raw run metadata.

Customer-app route
/flow-runs/[runId]
Who uses this
Every authenticated team member.

What it is

A single Flow run's complete picture. Use it to debug a failed run, audit what was written back, or confirm a successful run actually scored what you expected.

What you can do here

  • Read the summary tiles — duration, students analyzed, Writeback rows landed.
  • See the per-student outcomes — anonymous IDs with their resulting scores.
  • Read errors — when status is failed or partial.
  • Inspect raw metadata — for support diagnostics.

Common workflows

Diagnose a failed run

  1. Open the failed run from /schedules or the dashboard.
  2. Read the Errors section — most errors are Slate-side (auth expired, query offline).
  3. Fix in Slate. Use Run now on the parent Flow to retry.

Confirm the Writeback landed

  1. Open the run.
  2. Pick a student row.
  3. Open them in Slate and verify the ss_celia_* fields show the expected values.

Common gotchas

Throughput is zero but status is "completed"

The In Progress query returned no rows that passed Celia's pre-flight no-PII checks. Verify the query's filters, then re-run.

"Partial" status

Some students scored, some hit a per-row error. The Errors section lists the failed IDs. Most partial runs are caused by missing fields — populate them in Slate and retry.