## TL;DR
Find the step where the request stopped moving before you resend or recreate it, because a fresh request will stall at the same step. Open the request timeline, note the last completed step and the pending step owner, and check whether the stall is an approver who never got notified, an integration call to a downstream system that timed out, or a condition in the flow waiting on data. Nudge or repair that one step, confirm the request advances, and add monitoring for requests that sit past a threshold so the next stall is caught by the team, not the requester.

```text
Okta access request approval flow failed: request timed out error troubleshooting
```

## Use this when
- Access requests remain in a pending state well past the normal approval time.
- Requesters report a timeout message when submitting or tracking a request.
- Approvers say they never saw the request.

## Not for this skill when
- The request was denied and the requester disagrees. That goes through the appeal or resubmission route.
- The catalog item itself is broken for everyone at submission. Fix the item configuration first.

## Steps
1. Open a stalled request and copy its timeline, marking the last completed step, the pending step and how long it has waited at that step. Verify: the stall point is pinpointed to one step.
2. Check the pending step owner inbox and notification: confirm the approver was notified by finding the notification event in the Okta system log for this request. Verify: notification delivery is confirmed or its absence is proven.
3. If the step calls an integration or downstream provisioning, open that system job or log for the request reference and read its timeout or error entry. Verify: any downstream timeout is captured with its own error text.
4. Resolve the step cause: reassign to an acting approver, fix the downstream job credential or capacity issue, or supply the missing data the step waits on, recording which applied. Verify: the step cause is fixed and documented.
5. Advance the original request if the platform allows an admin nudge or retry of the step, and watch it move to the next step or to completion. Verify: the request state changes from its stalled step.
6. Submit a fresh test request for the same item and walk it through every step to prove the flow now completes within the normal time. Verify: the test request completes end to end.
7. Set an alert or report for requests pending beyond the agreed threshold per step, reviewed weekly during the access review period, so stalls surface proactively. Verify: the pending age report exists and has a named reviewer.

## Why it happens
Access request flows chain human approvals with automated provisioning, and a timeout label can come from either world: an approver notification that never arrived, or a downstream call that hung. The request timeline separates the two in seconds, but teams often restart requests blindly and lose that evidence. Repairing the actual stalled step, whether it is a person routing problem or an integration problem, fixes the flow for every later requester, and age based monitoring converts future stalls from user complaints into operational tickets.

## Variants and edge cases

### Okta access request stuck pending approval
The pending phrasing. Start at the timeline; the pending step owner field usually names the problem.

### request catalogue item times out on submit
The submit phrasing. A submission timeout with the request actually created is a display problem; check before resubmitting to avoid duplicates.

### approval flow integration timeout provisioning step
The integration phrasing. The downstream system log holds the real error; the flow only reports that it waited too long.

Edge cases to check before closing the review cycle:
- Duplicate requests created by impatient resubmission need merging decisions. Close duplicates with a reference to the surviving request.
- Approver on extended leave stalls every flow that names individuals. Prefer group or role based approvers in flow design.
- Timeouts that cluster at month end may be downstream capacity. Share the pattern with that system owner rather than tuning the flow alone.

Compatibility: Okta Access Requests and Identity Governance flows, Okta system log, downstream provisioning integrations.

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst__E9VtK8Yk1vxjqO6LMIU3g