Authentication → Flows. Lists every flow your tenant has — system flows (shipped, can't be deleted) and custom flows you've created.
What the list shows
Each row:
Name — the flow's name.
Kind —
systemorcustom.Trigger event — the platform event that runs this flow (
auth.login.submitted,auth.signup.submitted, etc.).Action count — total Actions attached across all trigger slots.
Last 24h run count — how many times the flow ran today.
Last 24h failure rate — % of runs that ended with an Action returning block or error.
Filters
Kind — system / custom / all.
Action count — > 0 (only flows with custom logic) / = 0 (flows running platform defaults).
Failure rate — sort by failure rate to find flows whose Actions are misbehaving.
What to do from here
Click a row → opens the Flow builder for that flow.
Click "Recent runs" on a row → opens the run history for that flow (last ~1000 runs, with per-run outcome + duration + Actions executed).
Click the menu (kebab) → enable / disable the whole flow (rarely useful for system flows; common for custom flows during incident response).
System flows
The flows your tenant ships with:
Flow | Triggers | Default Action count |
|---|---|---|
|
| 0 (platform defaults run; no custom Actions) |
|
| 0 |
|
| 0 |
|
| 0 |
|
| 0 |
|
| 0 |
|
| 0 |
|
| 0 |
All 0 by default. As soon as you attach an Action, the count bumps.
Custom flows
You usually don't need a fully custom flow — attaching Actions to system flows handles 95% of cases. But for edge scenarios (a specific application's onboarding has different needs), you can clone a system flow as a starting point and customise the slots.
Flows → New flow → Clone from . The cloned flow runs alongside the original (you choose which applications opt into it via the application's authentication policy).
Use sparingly. Drift across many custom flows is a real maintenance cost.
Disable a custom flow
Custom flow detail → menu → Disable. Disabled flows are skipped on the trigger event; the system flow takes over. Re-enable any time.
You can't disable system flows — they're the default path. To "disable" their custom Actions, detach the Actions one by one.