DBSync Cloud Workflow Error: Missing Referenced Record Causing "Task Needs Attention" Failures
1. Summary / Introduction This article explains how to troubleshoot DBSync Cloud Workflow tasks marked as “Needs Attention” when a transaction references a record that cannot be found in the target system. The issue occurs during the Transform and Write operation when DBSync attempts to use an object ID that cannot be located in the target environment. Because the referenced record is unavailable, the workflow task fails and requires attention. This article describes how to identify the missing reference using workflow logs and how to restore normal workflow execution.
2. Problem / Issue Synchronization fails during workflow execution when DBSync processes a transaction that references another record required for the operation to complete. During the Transform and Write step, DBSync attempts to resolve the referenced object ID in the target system in order to update or create the related record.
If the referenced object ID cannot be located in the target system, DBSync cannot complete the Transform and Write operation for the transaction. As a result, the workflow task fails during execution and is flagged as Needs Attention, preventing the affected record from being processed successfully.
4. Symptoms
The following errors may appear in the DBSync logs:
DBSync Cloud Workflow Error: X Number of task(s) needs your attention
TransformAndWriteCommandAction – Failed to process Transform and Write action
Object "8000122F-1680013967" specified in the request cannot be found.
During workflow execution, one or more tasks may be flagged as Needs Attention in the DBSync Cloud Workflow interface. The failure occurs during the Transform and Write step when DBSync attempts to process a transaction that references another record required for the operation.
When this condition occurs, the specific transaction associated with the referenced object ID fails to process. Tasks associated with that record are marked as requiring attention and the affected record remains unsynchronized.
In most cases, the issue is isolated to the specific transaction or records referencing the object ID, and other records in the workflow may continue processing successfully if they do not depend on the missing reference.
5. Root Cause The failure occurs when a transaction references a dependent record that does not exist or is not accessible in the target system at the time of processing. Because the referenced record cannot be found, DBSync cannot resolve the associated object ID required for the transaction.
This situation typically occurs when the referenced record:
• Was deleted from the target system • Was marked as inactive or disabled • Was never synchronized before the transaction referencing it was processed
Since the required reference cannot be resolved, DBSync cannot complete the operation and the workflow task is flagged as Needs Attention.
6. Solution / Resolution:
Log in to the DBSync Cloud Workflow environment.
Navigate to the Project that contains the workflow where the failure occurred.
Open the Workflow Task that is marked as Needs Attention.
Access the Execution Logs or Task Logs associated with the failed task.
In the logs, locate the Severe error entry related to the failure.
Identify the workflow step number shown in square brackets within the log entry. Example: [7] TransformAndWriteCommandAction – Failed to process Transform and Write action The number inside the brackets represents the exact workflow step where the failure occurred.
Review the error message in the same log entry and locate the referenced object ID shown in the error. Example: Object "8000122F-1680013967" specified in the request cannot be found. The value inside the quotation marks is the object ID of the record that DBSync attempted to reference in the target system.
Determine the integration direction of the identified workflow step in order to identify the target system where the record should exist.
Using the object ID obtained from the logs, search for the corresponding record directly in the target system.
Verify the status of the record and determine whether one of the following conditions applies:
The record exists and is active
The record exists but is marked as inactive
The record was deleted from the target system
The record never existed or was never synchronized
Based on your findings, perform the appropriate corrective action:
If the record should exist
Restore the record if it was deleted.
Reactivate the record if it is marked as inactive.
Recreate the record in the target system if necessary.
If the record should have been synchronized automatically, perform a re-synchronization of the master or dependent record.
If the record was intentionally removed or should not exist
Review the workflow logic and data source to determine why the transaction is referencing the record.
Consult the system owner or responsible team member to confirm whether the transaction should still be processed
Confirm that all dependent records referenced by the transaction exist and are accessible in the target system.
After resolving the reference issue, return to DBSync and re-run the failed workflow task or execute the workflow again to allow the transaction to process successfully.
7. Additional Troubleshooting (Optional)
If the issue persists after following the resolution steps, perform the following validation checks:
• Verify that all master or dependent records required by the transaction exist in the target system before the workflow processes the related transactional data.
• Use the object ID referenced in the workflow logs to perform a direct record lookup in the target system and confirm whether the record exists and is accessible.
• Confirm whether the referenced record is currently active, as records marked inactive or disabled may not be available for processing by the integration.
• Review recent data changes in the target system to determine whether the referenced record was deleted, deactivated, or modified, which may have caused the reference to become invalid.
• Validate that master data synchronization occurs before transactional data synchronization to prevent transactions from referencing records that have not yet been created in the target system.
• If the referenced record should exist but cannot be located, review previous synchronization runs or logs to confirm whether the record was successfully created in the target system.
8. Impact When this issue occurs, the workflow tasks associated with the affected transaction fail and are marked as Needs Attention in the DBSync Cloud Workflow interface. Transactions that reference the missing record cannot be processed because the required object ID cannot be resolved in the target system.
The impact is typically isolated to the specific records that reference the missing object, while other records in the workflow may continue processing normally if they do not depend on the unavailable reference. The affected transactions remain unprocessed until the referenced record is restored, synchronized, or otherwise made available in the target system.
9. Keywords DBSync
DBSync Cloud Workflow
Workflow Task Needs Attention
TransformAndWriteCommandAction
Transform and Write Step
Object specified in the request cannot be found
Referenced Record Not Found
Missing Referenced Record
Object ID Reference Error
Workflow Execution Logs
DBSync Workflow Logs
Record Dependency Error
Target System Record Missing
Integration Workflow Failure
Transaction Reference Error
Workflow Task Failure
Last updated