Troubleshooting ConnectALL Failed Record Sync Operations

Products

• ConnectAll SaaS
• ConnectALL
• ConnectAll On-Prem

Issue/Introduction

This article outlines the procedure for identifying and re-processing failed record synchronizations in ConnectALL SaaS. It addresses common mapping errors and retry procedures.

• Symptoms:
  • Sync flows failing due to field mapping errors.
  • "Parent data was not an object" errors in JIRA.
  • Need to re-process specific items without triggering a full system synchronization.

Resolution

1. 1. Log in to the ConnectALL administrative interface.
   2. Navigate to the Activity Monitor tab.
   3. Filter for "Failed" records.
   4. Select the relevant records and click Retry.

Note: If the retry fails due to cached metadata, update the record in the source system (e.g., Rally), then perform a specific update sync rather than a full sync.