Some tasks fail with timeout error

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

8.4p2

Share all details about your problem, including any error messages you may have received.

Some of the scheduled tasks that we have configured in our system are failing while being executed due to a timeout error.

In our setup we have two UI servers and two task servers. The host which is triggering time out is one of our task servers but is working as normal.

The error is the following:
The '{taskName} task ended with error.

Started : 4/1/26, 9:00:00 AM CEST Completed : 4/1/26, 9:05:09 AM CEST

Waiting for scheduled request to be started Timeout waiting for request on host: {hostname}.

Thanks for the help!

2

@unai-identic It indicates that task server threads were not assigned to the task and it eventually timed out waiting for the thread.

How many task servers you have? Also, check your server configuration and requestdefinition to make sure thread sizing is accurate.

3

Hi,

Sorry for the late response, I didn’t get a notification.

We have two UI servers and two task servers in place. What should I exactly check in the server configuration? And where is the requestdefinition set, with which value?

Thank you for the support!

BR,
Unai Puelles

4

@unai-identic go to Debug → object type as RequestDefinition. Here check for Aggregate Partition or Identity Refresh Partition, and see the threads allotted. Also check other definitions like for certification, rule request, group aggregation, etc.

5

Hi,

We have Aggregate Partition set to 1 and Identity Refresh Partition set to 4. Shall we increase this?

Thank you for the support.

BR,

Unai Puelles

6

@unai-identic Yes. Please try adjusting the numbers. You can start by changing the number equal to the number of cores per server. Let’s say you have 4CPUs, for 2 server.. you can set maxThreads to 4.. In this way it can create 4 partition per server and total 8 partitions. Please refer this article: https://community.sailpoint.com/t5/Other-Documents/Partitioning-Best-Practices/ta-p/74964

Give it a try and see if it helps.

7

Good morning Panda,

I see that for example in RequestDefinition object, for Rule Request we have the value set to -1. Is this a valid value, could this be set for a valid reason maybe to avoid issues that we had in the past?

In addition, we have tasks which we have a host set, shall we also empty the value so IIQ can handle the execution host depending on the load of each server? Could this be also a reason of this issue?

Thank you in advance and best regards,

Unai Puelles

8

@unai-identic -1 typically represent no restriction within IIQ. It means it can use as many threads as the server’s cpu/thread allows.

You can try removing the host from task definition and let IIQ allocate the host as per availability.

9

@unai-identic - The timeout errors you’re seeing in SailPoint IIQ tasks, especially in a multi-server environment (2 UI, 2 Task servers), are often caused by inefficient resource allocation or “bottlenecks” where one server is overloaded while others sit idle.

The -1 value should be replaced with a conservative limit (e.g., 8-10) to prevent resource exhaustion. You should definitely remove the hardcoded Host from your task definitions to allow for proper load balancing across your two task servers. Finally, ensure your maxThreads in the RequestDefinition is tuned to utilize both servers (e.g., total threads = 2 servers x cores per server), and verify that your database connection pool can handle the increased concurrency.