When an Access Request is configured to run a workflow automatically, if there is no request Assignee, the workflow may not run automatically, and the request gets stuck waiting for the workflow action to execute.
- Access Request Types
- Resource Centric Access Requests (RCAR)
- Okta Workflows
This will occur if the Workflow action is configured to map the Request assignee's email address to an input in the delegated flow, but an Assignee has not been specified.
It can occur for access requests that were created using Access Request Types or Resource Centric Access Requests (RCAR), as they both allow for mapping the Request assignee's email address to a delegated flow input, as shown in the following screenshots:
- Access Request Types
- Resource Centric Access Requests
If the request Assignee's email address must be passed into the delegated workflow, ensure an Assignee has been specified for the request.
For Access Request Types, request Assignees are always a member of the team that owns the Request Type and can be auto-assigned from the team Settings page:
For Resource Centric Access Requests, request assignees are always Super Administrators or Access Requests Administrators. By default, request assignees are not assigned automatically and currently must be set manually.
If an access request is stuck at a workflow action that was configured to run automatically because there is no request assignee, an Assignee can be specified manually at which point the workflow action should execute.
