I have raise request in request center and after submitting the request it is showing that request submiited successfully.
But after making request nothing is showing in the My request.
getting error in “Account Activity”
An unexpected error occurred: java.lang.NullPointerException: Cannot invoke “sailpoint.object.IdentityRequest.getRequesterId()” because “identityRequest” is null
In SailPoint ISC, this may occur due to a backend request processing failure where the Identity Request is not persisted correctly. Please retrieve your identity details via the ISC API and check for any data irregularities and try again.
Can you please explain in more which API you taking about ?
Hi @vikas,
This usually happens when the request shows success in the UI but is not actually persisted in the backend, which then causes the My Requests and Account Activity views to break.
In SailPoint Identity Security Cloud, the error:
java.lang.NullPointerException: Cannot invoke IdentityRequest.getRequesterId() because identityRequest is null
typically indicates a backend processing issue where the Identity Request object was not created properly after submission.
A few things you can check:
Try reproducing and check Audit / Activity logs around the same timestamp
Verify if the request appears via /v3/search API (if it’s missing, it confirms it was never persisted)
Check if this is happening for all users or only a specific identity (helps isolate data issue vs system issue)
If persistent, it could be a backend service issue and may need to be raised with SailPoint support
Since the UI shows success but backend data is null, this is likely not a UI issue but a request processing failure.
@vikaspawar0303 Please check your identity through which you are raising request, if there is some missing information and any irregularities.
Hello Vikas,
That NPE on IdentityRequest.getRequesterId() usually means the request never got created on the backend, even though the UI says “submitted successfully.”
POST /v3/access-requests is async. It returns 202 as soon as it accepts the payload, not when the request is actually created. So that success message just means it hit the queue, not that it exists.
I would start with a quick check:
GET /v3/access-request-status?requested-for=<identity-id> → see if the request shows up at all
GET /v3/account-activities?requested-for=<identity-id> → same check from activity side
In UI Search: status: Pending AND "Access Request" → check if it’s stuck instead of missing
If nothing shows up in the first two, then it never got persisted.
Next, try to isolate it:
Submit the same request for a different identity
Try a different requestable item
If it only breaks for one combo, it’s likely data-related (deleted/recreated item, missing owner, bad identity data). If it fails everywhere, it’s a tenant-level processing issue & only support can fix it.
Also double check the access item itself:
Still exists (wasn’t deleted & recreated)
Marked as requestable
Has a valid owner
If the APIs confirm nothing was created, there’s nothing you can fix from your side. At that point, raise a support ticket with the timestamp & identity ID.
Plz let us know what you see from the API calls & we can narrow it down.
You can retrieve the details of the raised user requests using the endpoint:
https://sailpoint.api.identitynow.com/v2025/identities/:id.
After fetching the response in Postman, review all identity attributes and check for any irregularities in the user’s identity data.
Hi,
This looks like the request is getting submitted, but something is failing while creating or retrieving the IdentityRequest object.
The NullPointerException on identityRequest usually points to a backend issue where the request is not being persisted correctly.
A few things you might want to check:
Since it’s also failing in Account Activity, it seems like the request object itself might be missing or incomplete.
You might need to check logs or raise this with support if nothing obvious shows up.
Thanks!
Hi Vikas,
Please let us know if you found any solution for this issue. We are facing the same problem as well.
Did you end up resolving this? Or Opening a SailPoint ticket? I’m seeing it as well now.
This usually indicates a corrupted or incomplete IdentityRequest object in SailPoint ISC/IIQ. The request gets submitted, but the backend fails while loading request history because identityRequest is null.
Check:
custom workflows/rules around request submission
DB consistency for IdentityRequest tables
task/server logs during request creation
Most cases require SailPoint support or backend cleanup if the request object was partially created.