Flow input and output (IO) data — every card has configurable settings plus input/output values. Opting to Save flow data lets Okta record the specific data passing through each card during execution, so you can review every card's values afterward.

Flow metadata — Okta records metadata for every execution event regardless of the Save flow data setting, including the type of flow, the execution timestamp, and the final execution status.

Low-latency (lightning bolt) — every card in the execution ran efficiently, so the flow ran in low-latency mode. This is common for latency-sensitive webhook and API Endpoint use cases.

Standard (dash) — the execution ran at a standard rate because it contains a card ineligible for low-latency mode.

Throttled (exclamation mark) — the execution experienced higher latency from resource constraints. Once throttled, a flow remains in throttled mode for 15 minutes and isn't eligible for low-latency mode during that time.

All standard — every execution contains a card that doesn't qualify for low-latency. All low-latency — every execution ran efficiently. Mixed — only some executions were low-latency; check the flow for cards you can modify to remove the latency issue. All throttled — every execution exceeded resource limits.

→ Assuming flow metadata (type, timestamp, final status) requires the Save flow data option — it's recorded regardless. Only the per-card IO data depends on that setting.

→ Treating a single "Standard" execution as a sign of a persistent problem — a lone card ineligible for low-latency is enough to mark that one execution Standard, without any resource constraint being involved.