okta-workflows-execution-limits

Diagnose and plan around Okta Workflows platform execution limits and resource quotas.

1|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill okta-workflows-execution-limits-theviziusgroup
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: okta-workflows-execution-limits
Source: https://github.com/TheViziusGroup/vibe-engineering-skills/tree/main/plugins/okta-workflows/skills/okta-workflows-execution-limits
Command: npx skills add https://github.com/TheViziusGroup/vibe-engineering-skills --skill okta-workflows-execution-limits-theviziusgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Okta Workflows enforces hard platform limits, plan-gated flow counts, automated throttling, and export rate caps that can silently break or degrade automation. This Skill gives you the exact numbers, error messages, and behaviors so you can diagnose limit-related failures and design flows that stay within the resource model. ## Core Features & Use Cases - Hard Limit Reference: Covers 100 MB instance memory, 2,000,000 max steps per flow, recursion limit 250 ("Stack limit exceeded"), 1 MB execution-history payload, 10 invocations/sec/flow rate limit, 30-day history retention, and file size caps. - Plan Gating & Throttling: Explains active flow counts by plan (Starter 5, Light 50, Medium 150, Maximum unlimited) and the automated flow throttling feature that limits resource allocation without stopping completion. - Export Rate Limits: Details the 15-minute export window with plan-based caps (Starter 10 through Maximum 1000) where exceeding the cap fails the entire export. - Use Case: A flow fails with "Stack limit exceeded" during a recursive helper-flow chain. Use this Skill to identify the 250 recursion limit and restructure the flow to iterate instead of recurse. ## Quick Start Ask the AI to explain why your Okta Workflow shows "The data returned successfully, but is too large to display" and whether it indicates a failure.

Frequently Asked Questions about okta-workflows-execution-limits

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What causes the Stack limit exceeded error in Okta Workflows?

The Stack limit exceeded error occurs when a flow exceeds the recursion limit of 250 nested calls, typically from recursive helper-flow chains. Restructure the flow to use iteration or streaming instead of deep recursion.

Is "The data returned successfully, but is too large to display" an error in Okta Workflows?

No, this message is explicitly not an error. It appears when an execution-history message exceeds the 1 MB payload limit, meaning the data cannot be displayed in history, but there is no impact on the actual data or flow execution.

How many active flows can I have on my Okta Workflows plan?

Active flow counts are plan-gated: Free Trial/Starter allows 5, Light allows 50, Medium allows 150, and Maximum is unlimited. Legacy Advanced Lifecycle Management entitlements allow 100 parent flows, and turned-off flows do not count.

Why is my Okta Workflow running slower than expected?

Okta's automated throttling may have limited your flow's resource allocation after it exceeded expected CPU time, table requests, memory, or helper-flow counts. The flow still completes, and Free Trial/Starter plans have lower throttling thresholds.

What are the Okta Workflows export rate limits?

Export capacity resets every 15 minutes with plan-based caps: Starter 10, Light 100, Medium 300, and Maximum 1000. Exceeding the cap fails the entire export with no partial output.

What is the Okta Workflows flow execution rate limit?

Each flow is limited to 10 invocations per second; exceeding this returns a 429 response. Design event-driven flows with queuing or batching to stay under this per-flow rate limit.