Check execution history
Okta keeps a history of your flow executions over the previous 30 days. You can enhance this history by choosing to save all the data that passes through the flow each time it runs.
For a newly created flow, in the Save flow dialog, enable the option to Save all data that passes through the flow.
For an existing flow, use the flow state button on the navigation bar to turn on the data saving feature:
-
Click the flow state dropdown to open the flow options.
-
Set the Save all data that passes through the flow option to active.
The flow state button changes to display Saving data
To stop saving data for an existing flow, complete these steps:
-
Click the flow state dropdown to open the flow options.
-
Set the Save all data that passes through the flow option to inactive.
The flow state button changes to display Not saving data.
To clear saved data from your execution history, see Clear all saved data.
View execution history
If you immediately triggered a flow after turning it on, you may not see the record in the execution history. Wait one minute and reopen the Execution History page.
With the save data feature active, you can select any result to see its full history:
-
The status, start time, duration, and latency details of the flow. See View Execution History details.
-
On the main page, the input and output fields show the values returned during the flow execution.
-
If calls to other applications supplied raw error content, that information is included for debugging purposes.
-
Successfully executed cards show a green check mark and the time that the card took to successfully execute.
-
If the flow stopped or failed, the card containing the invalid data is marked with an error.
You can also collapse the Execution History pane to give more space for the main page.
Search filter
You can run a full-text search across all execution histories for a single flow. You can search for data passed through any card, returned error text, card names, or input and output labels.
Okta Workflows supports the following special characters:
| Special character | Behavior | Example | Sample match | Notes |
|---|---|---|---|---|
| + | Acts as the AND operator | Workflows + Okta | Workflows is an amazing product at Okta | Spaces in phrases that aren't enclosed in quotation marks are assumed to be AND searches. |
| | | Acts as the OR operator | Workflows | Okta |
Workflows is an amazing product Or: Okta makes identity easy |
|
| * | Acts as a wild card | Workfl* | Workflows | Partial matches aren't included in the results unless the * is used. |
| "" | Wraps several terms into an exact phrase | "I love Workflows" | I love Workflows | |
| () | Wraps a clause for precedence | (Okta | Workflows) + love |
I love Okta Or: I love Workflows |
|
| ~n | Set search fuzziness, when used after a term | Warkflews~n | Workflows | Where n is a positive integer. |
| - | Negates a term | Workflows -Okta |
I love Workflows But not: I love Okta Workflows |
Execution status filter
Execution history also allows you to filter the search results according to the execution status.
| Status | Notes |
|---|---|
| All | Shows all results, regardless of the status. This is the default option. |
| Error | Flows that resulted in an error, and didn’t complete successfully. |
| Success | Flows that completed successfully. |
| In Progress | Flows that haven't completed. |
| Throttled | Flows that were throttled during execution. See Execution limits. |
|
Canceled |
Flows that have been canceled. See Cancel a flow execution. |
Date or time range filter
You can also filter the results to a single hour using the date and time filter. Click the calendar icon in the right panel of the Execution History page.
Use the From and To fields to set the date and time range for your query. The default shows all executions available up to the current day.
You can reset the filter by clicking the X next to the input field.