SailPoint Connector timeout
A connector operation timed out before completing.
Timeouts point to slow or unreachable targets, network issues, or too-large batches. Check connectivity and reduce load.
- Symptom: A connector operation timed out before completing.
- Most likely causes
- Step-by-step fixes
- How to prevent recurrence
A connector operation did not finish within its allowed time and was aborted. Timeouts point to something slow or unreachable, the target, the network, or an oversized batch, rather than a logic error.
Start here: read the evidence
Check the task or provisioning result for the timeout, then test raw connectivity to the target independently of IdentityIQ. Separating "can I reach it at all" from "is it slow" narrows the cause immediately.
Likely causes, in order
- Target slow or overloaded, especially during its own peak hours.
- Network latency or firewall drops on the path to the target.
- Batch or page size too large, so a single request takes too long.
- Timeout set too low for a legitimately large operation.
How to fix it
- Test connectivity/latency to the target from the task or VA host.
- Reduce the page/batch size so each request completes faster.
- Increase the connector timeout only if the operation is genuinely large and the target is healthy.
- Schedule heavy aggregations off-peak to avoid target load.
- Check target-side performance with its administrators.
Preventing recurrence
Right-size batch/page sizes for each source, schedule heavy jobs off-peak, and monitor connector run times so a gradually-slowing target is noticed before it starts timing out.
Common pitfalls
- Guessing instead of reading the task/transaction result, which usually names the cause.
- Fixing the symptom, not the root cause, so it returns.
- Changing several things at once, so you cannot tell what worked.