Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.
Please consider addressing the following when creating your topic:
What have you tried?
What errors did you face (share screenshots)?
Share the details of your efforts (code / search query, workflow json etc.)?
What is the result you are getting and what were you expecting?
I have noticed that since December 17th 2025 access requests in ISC are getting stuck at SOD or with approvers.
Even when approvers approve the requests in ISC it still shows that it is pending for approval.
I have tried reassigning that request to another to see if it allows the new approver to approve. It does not show up in new approver approval dashboard.
Not sure if any changes are done in the backend or not.
Before that access requests were getting provisioned successfully without any delay.
Would be great to know what needs to checked in this scenario?.
That could be because of too many workflows in execution state. They may not necessarily your own WFs but internal. if its in your non-prod instance, try to close the existing access request request and see the analyze the wait time.
Not sure if it’s stuck or queued as the access request is approved by the approver. But when requester or Admin is tracking the request it shows that it is pending with approver even when approver has already approved the request.
This may be related to a performance issue.
Please go to Monitor page and check the WPS. It may be processing a large number of requests.
Also, check the Search page to see if there are any sources that might have cycling sync attributes.
I’ve seen this behavior before; the problem was related to Active Directory attributes that were being synchronized cyclically (the same attributes every time the account was aggregated).
Two important checks that cut through the UI noise:
1.Validate the real status via API (not the UI).
Use the Access Request Status endpoint to see whether ISC thinks it’s still pending or already moved past approval. If the API shows it’s approved/processing while UI says “pending approval,” that’s a UI lag/processing backlog symptom (and a good data point for Support).
2.Look for workflow processing backlog + the root cause.
On the Monitor page, if WPS/workflows are processing a large queue (as Kevis noted), the next thing to check is “churn” sources: AD is a common culprit when attribute synchronization keeps re-updating the same attributes every aggregation, triggering repeated identity processing and starving request progression.
Fix is to identify the noisy source/attributes and stop the cyclic updates (exclude volatile AD attributes from sync, fix mappings so the same values aren’t rewritten every run).
If after those two checks the API still shows the request stuck at approval with no progression, it’s time for a Support ticket with the request Trace ID and the Monitor evidence.
The reason why Access Requests were taking time because there were lots of old items which are stuck due to missing permission for a source. After fixing the permission problem all the queued by Items got cleared now.
Thank you for all your valuable inputs on this topic.
Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.