View Execution History details

The Details column in your Execution History pane provides you with more information about your flow executions. For example, if the flow executed in standard mode, low-latency mode, or if it was throttled. Okta assigns each flow execution a specific icon to help you quickly identify flows:

Flow details: image of a lightning bolt indicating flow executed at the low-latency rate. - Low-latency

Flows with the lightning bolt icon contain only cards that execute efficiently on a consistent basis in low-latency mode. Generally this occurs for latency-sensitive webhook and API Endpoint use cases. See Low-latency flows.

Flow details: image of a dash mark indicating flow executed at the standard rate. - Standard

Flows with only a dash executed at a standard rate. Any flow with a standard rate contains a card that is ineligible for low-latency mode.

Flow details: image of an exclamation mark indicating flow executed at the throttled rate. - Throttled

Flows that ran in throttled mode experienced higher latency due to resource constraints. Throttled flows aren't eligible to run in low-latency mode.

Common scenarios

Flow details: image of a set of flow executions, all with dash marks indicating the flows executed at the standard rate.

All standard

All flow executions completed in standard mode. This means that your flow contains a card that doesn't qualify for low-latency mode.
Flow details: image of a set of flow executions, all with lightning bolts, indicating the flows executed at the low-latency rate.

All low-latency

All flow executions completed in low-latency mode. See Low-latency flows.
Flow details: image of a set of flow executions, with mixed icons, indicating the flows executed at varying rates.

Mixed

Only some executions of your flow ran in low-latency mode. Review your flow to see if there are cards that you can modify to remove latency issues so the flow always runs in low-latency mode.
Flow details: image of a set of flow executions, all with warning icons, indicating the flows executed in throttled mode.

All throttled

All flow executions exceeded the resource limits and were throttled. After a flow is throttled, it remains in throttled mode for 15 minutes. See Execution limits.