Skip to content

Daily work

Flow detail

One Flow's full picture: configuration, recent runs, throughput, and the Run-now button.

Customer-app route
/flows/[id]
Who uses this
Every authenticated team member.

What it is

The detail screen for a single Flow. Tells you when it last ran, when it runs next, what it's configured to do, and how recent runs went.

What you can do here

  • Read the configuration — Slate Query — In Progress URL, Slate Query — Positive Outcomes URL, Slate Source Format — Writeback URL, cadence, use case.
  • Run now — kicks off an out-of-schedule run for testing.
  • Open recent runs — each run has its own forensics page at /flow-runs/[runId].
  • Edit cadence — jump to /flows/[id]/schedule.
  • Toggle dry-run mode — pause real writebacks while you debug.

Common workflows

Verify a brand-new Flow

  1. Open the Flow detail.
  2. Click Run now.
  3. Wait for the run to complete (usually under a minute for small batches).
  4. Open the run from the Recent runs list to inspect what was scored and what was written back.

Investigate a failure

  1. Open the failed run from Recent runs.
  2. Read the Errors section. Most failures point at a Slate-side config problem.
  3. Fix it in Slate, then click Run now to retry.

Common gotchas

Run now is disabled

The Flow is paused or another run is in flight. Wait for the current run to complete or unpause.

Configuration is locked

A run is currently in flight. Wait for it to finish — config edits during a run can corrupt the Writeback target.