WebServices connector with Partitioning- Retry the API call / Partition if it fails with 504

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

8.3 P3

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

WebServices Connector Application with Partitioning enabled :

  1. During aggregation (Partitioned Account Aggregation Operation), We are getting an HTTP Error ConnectTimeOut after some partitioning are completed

  2. How can we retry the specific errored api call. Are there any flags to be added in Application or TaskDefinition Objects for Retry mechanism?

  3. We are using cursor based pagination ( using nextCursor and hasMore in transient values)

2

I have never tried this for aggregation but you can give a try. add the below entry to the application from debug page.

<entry key="retryableErrors"> 
    <value> 
      <List> 
        <String>ConnectTimeOut</String> 
      </List> 
    </value>
</entry>

Regards
Ankush

3

No, this config is for provisioning failures.

4

@HarnishaM Workday connector using below entry to enable aggregation retries for the listed errors: errorsubstring

I am not sure if it will work for Webservice connector, but please try.

Also, is this error intermittent? or you are getting for every run. In that case, you might want to check your partitioning logic. If you do the execution without partitioning, is it working?

6

Hi Harnisha,

I don’t think IdentityIQ provides any built‑in option to retry aggregation calls, especially for partitioned aggregation

What can be done, however, is to optimise the aggregation to avoid the timeouts:

  • Increase the connection and timeout settings in the application.
  • Reduce the page size to around 100–200 so the API responds faster.
  • Reduce the partition size to around 1000 to break the aggregation into smaller, more manageable batches.
7

Hi @HarnishaM

I believe Webservices connector cannot handle this OOTB. You might have to either increase the timeout in application config xml or ask the corresponding application team to increase the timeout time.