<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
Okta Workflows Flow History Appears to Be Out of Date
Workflows
Overview
After configuring a Workflow to respond to an event hook, and taking the action that triggers that event hook, the flow has taken action as expected; but the flow history either does not reflect that execution of the flow, or shows as in progress.
Applies To
  • Okta Workflows
Cause

Flow execution and flow history are asynchronous. As each step of the flow is executed, the corresponding flow history events are written to a queue to be published to the flow history page. Because these actions are asynchronous, there are certain situations where the flow history will be delayed even when the flow is executed in a timely fashion.

Solution

Flow history should not be considered as a real-time monitor of Workflow executions and instead should be used to view historical executions and for purposes of troubleshooting or debugging flow configuration.

Loading
Okta Workflows Flow History Appears to Be Out of Date