Okta Workflows provides different methods to view flow step usage:  flow-level event data through Execution Log Streaming, and per-card details in History Inspector and this article provides details on the recommended method for monitoring step counts and identifying where the most steps are being executed.

• Okta Identity Engine (OIE)
• Okta Classic Engine
• Okta Workflows

What are the options for monitoring step counts in Okta Workflows?

The following options are ways to monitor step counts in Okta Workflows and identify where most steps are executed.

• Execution Log Streaming helps identify which flows have the highest step counts by capturing event metadata for all flows. Metadata can be tracked for every flow or just for specific high-risk or high-impact flows. This feature is useful for providing a detailed event history for analysis and alert activities.
• History Inspector provides a deeper look into where most steps are executed at the card level, with detailed metadata on the execution of any flow in the Execution History. Use this information to examine and resolve issues with flow optimization, resource usage, network latency, or overall flow execution speed.

Related References

• Workflows system limits