Automation is not picking up new records - ConnectALL
Article ID: 447212
Updated On:
Products
Issue/Introduction
In ConnectALL, an automation may fail to pick up or sync records, resulting in a processing count of "0" despite relevant issues existing in the source project. This typically occurs during the "SearchModifiedRecords" phase of the sync.
Symptoms
- The automation runs, but the processing count remains at "0".
- Other automations for different issue types (e.g., Bug or Story) work as expected.
- ConnectALL logs contain the following timeout error:
ERROR #### [#### | #### | #### | | {new_group}][Camel (camel-1) thread #### - Split] com.go2group.connectall.model.transformer.model.api.SearchModifiedRecordsTransformer: Failed to process modified records for automation: ####Caused by: jakarta.ws.rs.ProcessingException: java.net.SocketTimeoutException: Read timed out
Environment
- Jira Adapter
Cause
A read timeout is occurring on the Jira side. This is caused by enabling the Jira Sync with Changelog option on an automation that includes issues with very long history logs (e.g., Epics with 10,000+ child issues or extensive change histories). Jira is unable to complete the request for the changelog before the connection times out.
Resolution
To resolve this issue, use one of the following methods:
Disable Changelog Sync:
- Navigate to the Entity Mapping tab for the affected automation.
- Locate the Flow Properties section.
- Disable the Jira Sync with Changelog option.
- Save and re-run the automation.
Apply Exclusion Filters:
- Identify specific issues (e.g., Epic keys) known to have exceptionally large histories.
- In the automation Flow Filter, add a condition to exclude these specific issue keys.
- Save the automation and re-run the sync.
For assistance with retrieving logs or further troubleshooting, see . Scroll to the bottom of the page and click on your respective region.
Additional Information
Feedback
