Workflows system limits

Okta maintains a large set of SaaS connectors. These connectors handle API calls through a user-friendly, no-code interface, with optimizations such as built-in backoff and retry.

The maximum number of active flows you can run depends on your plan:

• Workforce Identity Cloud Free Trial: 5 active flows, with a maximum limit on flow executions.

• Workflows Starter: 5 active flows

• Light Workflows: 50 active flows

• Medium Workflows: 150 active flows

• Unlimited Workflows: Unlimited active flows

Flows that are turned off aren't counted against the limit. The limit is configurable on a per-org basis. See Flow limits.

If you have a legacy Workflows entitlement (for example, from Advanced Lifecycle Management), then you're limited to 100 active parent flows.

For the Export Flow or Export Folder function cards, your Workflows subscription plan determines the maximum number of flows that you can export. Your organization's available export capacity is reset every 15 minutes.

To perform a successful export, the number of exported flows can't exceed the assigned limit. Otherwise, the export fails, and no flows are exported.

The total number of flows counted includes flows located within any subfolders.

Flow limits don't apply to exports performed using the Export dialog from the folder sidebar.

Limit on the instance variables stored in a flow as part of its execution.

The amount of time that a flow can be paused as it waits for a person's or a system's response before it terminates.

The maximum number of steps that can be executed in a flow.

Workforce Identity Cloud Free Trial orgs have a limit on the number of flow executions over the duration of the free trial period. This limit is subject to change without notice.

There's no flow executions limit for orgs on the Workflows Starter plan, or the Light, Medium, and Unlimited plans.

Event and inline hook delivery have different rate limits (see following tables). However, if you're invoking a flow directly from the API, there's a limit of 10 invocations per second per flow.

After the limit is exceeded, Okta returns a 429 error code.

The maximum number of times a helper flow can call itself. Flows that exceed this limit receive the following error message: Stack limit exceeded.

If any single message in the Flow History exceeds 1 MB, it isn't stored. The entry in the output field is replaced with the following message:

The data returned successfully, but is too large to display.

The size limit on files inside flows for attachments used in action cards such as the Send Email with Attachment action card for the Gmail connector.

The size limit on files inside flows from download or upload action cards, such as:

• Upload Attachment action card for the Salesforce connector

• Upload File action card for the Google Drive connector

• Download Document in Envelope action card for the DocuSign connector.

The size limit on files transferred using the SFTP connector cards.

The maximum amount of time that any file can be stored in the Workflows file system.

The number of tables available in an org.

This limit is configurable on a per-org basis.

The maximum number of rows in a table.

You can't add a row to a table after you've reached the limit.

The maximum number of columns in a table.

You can't add a column to a table after you've reached the limit.

The size limit of a single Workflows table cell.

Attempting to update a table cell with an input that is larger than the limit returns an error.

Limit on the number of characters in a table cell.

For an incoming HTTP connection to an API endpoint that invokes a synchronous flow, the amount of time it waits before terminating the connection. However, the flow itself isn't terminated.

Okta event hooks have a completion timeout of three seconds with a single retry.

A request isn't retried if your endpoint returns a 4xx HTTP error code.

Any 2xx code is considered successful, and thus the request isn't retried. If the external service endpoint responds with a redirect, it isn't followed.

Okta limits each org to 400,000 applicable events within a 24-hour period. After your org reaches this threshold, further event hooks aren't triggered. The System Log receives a warning before hitting the event limit, when the number of events reaches 280,000. The event limit resets 24 hours after the first event.

If a request times out after three seconds, event hooks are retried once. Retries don't count toward the org limit.

A maximum of 10 active Event Hooks can be configured per org. Each event hook can be configured to deliver multiple event types.

A maximum of 100 events can be grouped with each event hook payload. Each event hook can be configured to deliver multiple event types.

Okta inline hooks have a completion timeout of three seconds with a single retry.

A request isn't retried if your endpoint returns a 4xx HTTP error code.

Any 2xx code is considered successful, and thus the request isn't retried. If the external service endpoint responds with a redirect, it isn't followed.

The maximum number of combined active and inactive automations for your org is 50.

The maximum number of groups per automation is 10.

The maximum number or concurrent requests from Workflows to the /api/v1/users/${id} endpoint.

This limit doesn't count against the concurrent Workflows requests limit.

The maximum number of concurrent requests from Workflows to an Okta org across all endpoints.

• 5x - 50 concurrent requests

• 10x - 80 concurrent requests

• 25x - 120 concurrent requests

• 50x - 150 concurrent requests