Okta lifecycle management deprovisioning hung on app, workflow failed
Unsticks Okta lifecycle deprovisioning hung on one app by isolating the hanging connector, allowing the workflow to continue, and cleaning up the leftover manually. Use when an LCM run stalls on a specific app. Not for runs that fail fast with a clear error.
TL;DR
One app's deprovision call is hanging, often a slow or dead target API, and the workflow waits on it. Configure the workflow to continue past that app's failure, resume the run, fix the connector, and handle the leftover account manually.
Okta lifecycle management deprovisioning hung on app, workflow failedUse this when
- An Okta LCM deprovision run stalls on one app step.
- The step shows in-progress for far longer than normal.
- Other apps in the same run completed.
Not for this skill when
- The step fails fast with an error. That is a different fix; read the error.
- All apps hang. That is a platform or network problem.
- The app step was skipped by design. Then nothing is wrong.
Steps
- Identify the hanging app in the run log. Verify: you know which step is stuck.
- Check the app's API health directly. Verify: you know whether the target is down or just slow.
- Configure the workflow to continue on that app's failure, or remove the step temporarily. Verify: the workflow can proceed.
- Resume the run. Verify: the remaining steps complete.
- Clean up the leftover app account manually and fix the connector. Verify: both are resolved.
Variant phrasings
Okta LCM hung
The short phrasing.
deprovision stuck on app
The state-first search.
app connector timeout
The cause-first phrasing.
Compatibility: Okta lifecycle management with app provisioning connectors.
Why it happens
LCM waits on each app step in sequence. A dead or extremely slow connector blocks everything behind it, turning one sick app into a stalled offboarding.
Edge cases / pitfalls
- The app actually deprovisioned the user but the response never arrived; check before retrying to avoid duplicates.
- Continue-on-failure masking a real problem; the manual cleanup step is mandatory, not optional.
- The connector timing out only under load; the hang may be intermittent.
- Removing the step permanently instead of fixing the connector; the coverage gap returns.
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_4BYylCbwH36zf1jsFI8W6g