Access has not been provisioned to the requested app for any of the users and when the requestor attempts to cancel the request he gets the following error:
“Trace ID: 5191e831bab74ea092b7986870d0415d
Details:
An error occurred. If you are unable to continue your work, please contact SailPoint support.
An internal fault occurred.”
Not understanding what would cause approval to hang like this?
There can be certain corner scenarios wherein the provisioning might be stuck. I might not be able to help out in identifying for which reason it has been stuck.
Thanks Aman, that’s really helpful. For the time being we have manually provisioned the access. Still trying to figure out why it is hanging.
I assume I can use this API call to cancel them and have the requestor repeat the request?
Yes, and I think there been a recent update wherein an admin now has the capability to govern the access requests initiated from Request Center.
For the request being stuck at provisioning tab I think you have to first begin with the connector type and if there are any rules involved and additionally monitor the logs on the VA.
I just copied and pasted “5191e831bab74ea092b7986870d0415d” into search. I tried it with and without quotations. I’m looking at wuery documentation but not seeing anything for trace ids.
I tried traceid, trace.id, and a few other things, but got nothing. I’ll try tracking id. I did put in a ticket, because it’s been causing some issues. Thanks for the advice.
Hey Aman,
I seem to have missed this when I initially replied. Can you tell me what exactly you mean by AccountRequest page? We had the user show us his pending request, that’s where I got the screen shot from. Is there somewhere else I should look?
We can check the AccountActivity within the search tab for the affected user and check if there was a plan generated (AccountRequest) for them. That info might help us out in determining what might have happened.
