ConnectALL: Retry Count is Not Increased on Partial Failure, Causing Endless Retries

Products

• ConnectAll On-Prem
• ConnectALL
• ConnectAll SaaS

Issue/Introduction

When a synchronization job experiences a partial failure in ConnectALL, the retry count is not increased, causing the failed transaction to be retried continuously without exhausting the retry limit set by the adapter.transaction.error.retry property. This results in the failed syncs repeatedly appearing in the user interface (UI) and logs.

Environment

 

• Affected ConnectALL Versions: 4.0.0.

• Customer Environment: On-Premise (OP), SaaS.

• Configured Retry Limit: adapter.transaction.error.retry is set to the default value of 3.

 

Cause

This behavior is due to a product defect (DE179010) in ConnectALL version 4.0.0. When retrying a partial failure, the retry count was being reset instead of incrementing, which led to the failure being retried indefinitely.

Resolution

This issue has been identified as a product defect and is resolved in the following ConnectALL versions:

• 4.0.1

• 4.1.0

The recommended resolution is to upgrade ConnectALL to version 4.0.1 or later to ensure that the retry count is properly incremented, and failed transactions stop after exhausting the configured number of retries (e.g., 3 times)

Additional Information

 

• The expected behavior is that the retry count should increase and stop after 3 attempts, or the number specified by the adapter.transaction.error.retry property.

• This defect also caused issues where a ConnectAllIssueLinkingException would repeatedly regenerate every cycle even when no new changes were being made.