Hi,
I’m experiencing with the connector provisioning feature. Although the feature is enabled on my end, whenever I submit an access request, it remains stuck in a pending status indefinitely.
Is the any reason?
is the any reason?
Thanks.
Hello KR. I would suggest first checking where the request is getting stuck, whether it is still waiting for approval or has moved to provisioning.
Go to Admin > Dashboard > Approval Management > Access Requests, open the request, and check the Process tab.
- If it is waiting for approval, check the Assignees tab to see who needs to approve it.
- If approval is completed, check Admin > Identity Management > Activities for the Account Activity status and any provisioning error.
- Also check Admin > Dashboard > Tasks in case a manual provisioning task was created.
If it has reached provisioning, try Test Connection and a manual account aggregation on the Oracle EBS source. These help check connectivity and read operations, but do not confirm provisioning works.
Could you share where the request stops, the Account Activity status/error (or whether no activity exists), and whether you are requesting a new account, responsibility, or role? Also, are Test Connection and aggregation successful, and does this happen only with Oracle EBS?
That should help us narrow down the issue before making any configuration changes.
Hi @KRK1
There could be several reasons for an Oracle EBS access request remaining in a Pending status:
- Approval workflow is still pending.
- The provisioning plan was generated but not submitted to the connector.
- Connector provisioning is enabled, but the provisioning task/queue is stuck or failing.
- Oracle EBS connector configuration or provisioning rules are encountering errors.
- Required account correlation or entitlement mapping is missing.
Could you please check the request details and share:
- The provisioning status/error from the access request.
- Relevant connector or provisioning logs.
- Whether approvals have completed successfully.
This will help identify the exact cause!!!
Hi,
A request stuck at Pending → Executing: In Progress with no approvals, manual tasks, or provisioning events usually means ISC hasn’t sent anything to the connector yet. The problem is more likely before the Oracle EBS connector or the VA. Please check these in order:
- Account Activity API: run
GET /v3/account-activities/91a2d89d1ce44c76aebe03aca16ae740and checkitems[].provisioningStatus,sourceId, and any errors or warnings. This shows whether the request reached provisioning or is still being processed inside ISC. - Search → Events: search by the request ID for a provisioning plan or a failed step. Share any error message.
- Source configuration: on the Oracle EBS source, confirm that create/update provisioning is enabled, the requested entitlement belongs to that source and is requestable, and the provisioning policy has no unresolved required fields.
If the activity shows the request reached provisioning, check the VA and connector logs next. Otherwise, focus on the source and provisioning configuration.
Hello KR. Thanks. Since there are no approvals or manual tasks involved, I would suggest checking whether ISC has actually attempted provisioning to Oracle EBS. The Pending / Executing: In Progress status does not necessarily mean the request has reached the connector. Could you please try retrieving the activity details using:
GET /account-activities/v1/{id}
Use the activity ID from your screenshot. In the response, check items[].provisioningStatus, sourceId, and any errors or warnings at the top level.
Depending on what you find:
- Committed: The request was sent to the connector. Check the VA
ccg.logaround that time for any related errors. - Retry / Failed: Check the activity errors and VA logs to understand what failed.
- No Oracle EBS item: I would first check ISC request processing and the source provisioning configuration.
- Pending at the item level: The action is still in progress, so I would check whether its status changes.
Could you share the API response (masking sensitive details), how long it has been in Executing, and whether you are requesting an account, responsibility, or role? That should help us narrow down where the request is getting stuck before changing any configuration.
@KRK1 -
Adding to what @punna0001 and @rameshcba said. With no approval, no manual task and nothing under Account Activity or Events, I’d assume ISC never sent anything to the Oracle EBS connector. Pull the activity with GET /v3/account-activities/{id} and look at items.provisioningStatus and items.sourceId. If there is no item for the EBS source, the problem is on the ISC side and not in the connector.
Two things to rule out from there:
-
A request that did reach the connector and succeeded still sits in Pending until it is verified. PROVISIONING_VERIFICATION_PENDING means approvals are done and provisioning is waiting to be verified (https://developer.sailpoint.com/docs/tools/sdk/python/v3/models/requested-item-status-request-state). As far as I know that verification happens on the next aggregation of the source, so run one and see if the status moves.
-
The EBS connector is only certified for on-prem EBS, so I’d expect the source to go through a VA cluster. Check the cluster is healthy and the VA logs show anything at the request time. If provisioning did run and failed, the usual cause is the service account missing write grants. On EBS 12.2.4 and later they have to be granted through AD_ZD.GRANT_PRIVS, see Troubleshooting and Required Permissions . That normally shows up as an error on the activity, though, not a silent Pending.
If the activity has no EBS item and nothing moves after 30 minutes or so, check Admin > Workflows for any disabled or failing workflow. One thread with a VA source stuck in Pending was fixed by re-enabling a disabled workflow ( JDBC connection - Provisioning state is on pending ). I haven’t confirmed that applies to your tenant. If it still doesn’t move, open a Support ticket with the trace ID. To clear the stuck request in the meantime, use the close-access-request API with Terminated / Failure, as suggested here: Approval hanging in the Provisioning stage
Here is the output I donot see any information here
{
“completed”: null,
“completionStatus”: null,
“type”: “appRequest”,
“requesterIdentitySummary”: {
“id”: “4639bbcbb421f3572”,
“name”: “test”
},
“targetIdentitySummary”: {
“id”: “2b11f5ddc6344c009e3ecd0fa719069d”,
“name”: “test123”
},
“errors”: null,
“warnings”: null,
“items”: [
{
“id”: “4c0781a51f8d4ba38244eec9b8b79158”,
“name”: “4c0781a51f8d4ba38244eec9b8b79158”,
“requested”: “2026-10-09T07:54:24.217Z”,
“approvalStatus”: “PENDING”,
“provisioningStatus”: “PENDING”,
“requesterComment”: null,
“reviewerIdentitySummary”: null,
“reviewerComment”: null,
“operation”: “ADD”,
“attribute”: “RESPONSIBILITIES”,
“value”: “23207~809”,
“nativeIdentity”: null,
“sourceId”: “c27266d10bae6889dc88e9”,
“accountRequestInfo”: {
“requestedObjectId”: “f334278cfb65327dae6ff71a94eee501”,
“requestedObjectName”: “Engine”,
“requestedObjectType”: “ENTITLEMENT”
},
“clientMetadata”: null,
“removeDate”: null
}
],
“executionStatus”: “EXECUTING”,
“clientMetadata”: null,
“id”: “91a2d89d1ce4f3aca16ae740”,
“name”: “49b65df413bb5df6d5dabfa1bd3”,
“created”: “2026-10-09T07:54:24.219Z”,
“modified”: “2026-10-09T07:54:24.219Z”
}
Hi KR,
In addition to @punna0001 and @officialamitguptaa
There could be some permission issue at source level. Could you please get this checked at source level and get this checked from the DBA as well that service account has necessary privileges to provision the same.
Thanks
Deepak
@KRK1 -
Thanks for posting the output. It points at the approval step and not the Oracle EBS connector. The item has approvalStatus PENDING with no reviewer, provisioningStatus PENDING, no errors, and modified is identical to created. Nothing has touched the request since it was submitted, so Test Connection, aggregation and VA logs won’t show anything for it yet.
“No approval set” can still leave you with an approval. One thread had an entitlement request sitting in Pending with SailPoint Support as the approver, even though approval hadn’t been enabled: SailPoint Support as Owner - for Request Approval in ISC . For your request, check:
- Admin > Dashboard > Approval Management > Access Requests, open the request and look at the Assignees tab to see who it is waiting on.
- The same via API: GET /access-request-approvals/pending, or the list-access-request-approvers endpoint, to see the approver.
- The approval settings for the “Engine” entitlement itself and the global Access Request Settings, since an entitlement request can pick up an approval from either.
Approving it from Approval Management as an admin should move it on in dev, and then you can fix the approval config so it doesn’t repeat.
If it clears approval and stalls again, the Oracle EBS side comes next. nativeIdentity is null on the item, so check whether test123 already has an EBS account. If not, ISC has to create one first, and that needs a create-account provisioning policy with the mandatory fields filled in.
Hello @KRK1. Both approvalStatus and provisioningStatus are PENDING for the Engine entitlement. I agree with Amit that approval is worth checking first, but I would confirm whether an approval is actually waiting.
Open the request under Admin > Dashboard > Approval Management > Access Requests and check the Process and Assignees tabs.
Approval can be configured at three levels (entitlement > source > global), so I would check:
- Entitlement: Engine > Access Requests > Require Approval
- Global: Global > System Settings > Feature Settings > Access Request > Entitlement Requests
- Source:
GET /sources/v1/{sourceId}/entitlement-request-config
Even if Engine does not require approval, a source-level or global setting could still apply. If an approval is waiting, you could approve an authorized test request in dev using More > Overwrite Current Approver > Approve Request, then check whether provisioning starts.
there is mandatory attibute that is missing in provisioning policy. now it is working fine.