This article provides troubleshooting steps that may resolve errors when attempting to launch the Okta Workflows Console.

• Okta Workflows

NOTE: 

• Accessing workflows requires Super Admin privileges or the appropriate Role-Based Access Control (RBAC) role (that is maintained). See Get started with RBAC.
• If the user is able to access the Workflows Console but cannot see the Flows or Connections tabs, see No Access to Flows or Connections Tabs in Workflows Console.

Error 403 or 500

1. Confirm that the SUPER ADMIN (or RBAC role) account has been assigned to both Okta Workflows and Okta Workflows OAUTH applications (Okta Admin portal > Applications > Applications > search for each and confirm that it is listed in the Assigned to Application tab).
   • Getting Error "403 Not Assigned App" when Attempting to Access the Workflows Console.
2. Try clearing the browser's cookies/cache.
3. Try a different browser.
4. Confirm in the system log that there are no entries for security.request.blocked an IP address from the Okta allow list.
5. CUSTOM DOMAIN related:
   1. Ensure that the Custom Domain is showing Active (Okta Admin portal > Customizations > Brands > select the brand > Domains section).
   2. Confirm the login to the Custom Domain to allow Okta Workflows authentication with the Custom Domain.
   3. Confirm that the CNAME is valid using any online site for CNAME lookup.

NOTE: For more info on Workflows + Custom Domain login behavior, check the Workflows Console Required to Authenticate Custom Domain documentation.

Error 400, 404, or (500 CONTINUED)

Please open a Support Case providing the information below:

• All users or some.
• Include the Okta tenant.
• Provide a screenshot of the error to include the ERROR ID (if any).