You are here:
Troubleshoot Failed Data Processing Engine Runs
When a run fails, find the error code on the Analysis tab in Monitor Workflow Services. Each error code maps to a specific resolution in this topic. This reference covers errors across data sync, data transformation, writeback, and runtime platform utilization.
Required Editions
| View supported editions. |
- Troubleshoot Data Sync Errors for Data Processing Engine Runs
A Data Processing Engine definition run can fail when data from the definition's data sources doesn't sync in the definition's runtime platform. Learn how to resolve data sync issues for definition runs. - Troubleshoot Data Transformation Errors for Data Processing Engine Runs
A Data Processing Engine definition run can fail when the runtime platform fails to transform data based on the definition's node configurations. Learn how to resolve data transformation issues for definition runs. - Troubleshoot Data Writeback Errors for Data Processing Engine Runs
A Data Processing Engine definition run can fail when the definition tries to write back results to the target objects. To check why a particular writeback task failed, use the Get Job Failed Record Results API. In the API URI, specify the failed task job's reference ID as the job ID. - Troubleshoot Runtime Platform Utilization Errors for Data Processing Engine Runs
A Data Processing Engine definition run can fail when the org reaches its provisioned Data Pipelines limits. Learn how to resolve runtime platform utilization errors for definition runs. - Troubleshoot Validation Errors for Data Processing Engine Runs
A Data Processing Engine definition run can fail when the Data Processing Engine tries to validate the input and output of the run's stages. Learn how to resolve validation errors for definition runs. - Troubleshoot Other Errors for Data Processing Engine Runs
A Data Processing Engine definition run can fail due to errors where the root cause isn't available. Learn how to resolve definition run errors where the reason is unknown.
Troubleshoot Data Sync Errors for Data Processing Engine Runs
A Data Processing Engine definition run can fail when data from the definition's data sources doesn't sync in the definition's runtime platform. Learn how to resolve data sync issues for definition runs.
Best Practices
Based on the data volume of the definition's data sources, select a data sync connection mode that suits the data size:
- If the data source has one million records or fewer, use the Incremental connection mode in CRM Analytics.
- If the data source has more than one million records, use the Full Sync connection mode in CRM Analytics.
- During peak business periods and for high-volume data sources, schedule daily or weekly manual data syncs.
Identifying Data Sync Issues
Identify definition runs where data sync failed by checking one of the following in the run's batch job in Monitor Workflow Services:
- The Details tab shows the execution status as Data Sync.
- The Tasks tab shows the status of a data source batch job part as Failed.
Fixes for Data Sync Errors for CRM Analytics Runtime
| Issue | Error Code | Resolution |
|---|---|---|
| A definition run fails because a user deleted a field previously included in a Connected Dataset from the object schema. | DATA_SYNC_ERROR_FIELD_REMOVAL | Remove the field reference from the CRM Analytics recipe, then run the definition again. Alternatively, if the field is still required, add it back to the definition. |
| A definition run fails because a data source node has no fields selected. | DATA_SYNC_ERROR_ALL_FIELDS_REMOVAL | Add at least one field to the data source node, or remove the node from the definition. Run the definition again. |
| A definition run fails because of a general Data Sync failure. | DATA_SYNC_ERROR | Run the definition again or manually sync the data sources in CRM Analytics. If the issue persists, contact Salesforce Support. |
| A definition run fails because DPE can't connect to the CRM Analytics Salesforce Connector. | DATA_SYNC_ERROR_CONNECTION_FAILURE | Run the definition again. If the issue persists, contact Salesforce Support. |
| A definition run fails because DPE can't retrieve the Data Sync job status from CRM Analytics. | DATA_SYNC_ERROR_POLL_FAILURE | |
| A definition run fails because DPE can't retrieve the Dataflow job IDs needed to track the Data Sync. | DATA_SYNC_ERROR_ID_RETRIEVAL_FAILURE | |
| A definition run fails because DPE can't enqueue the CRM Analytics Dataflow jobs for Data Sync. | DATA_SYNC_ERROR_ENQUEUE_FAILURE | |
| A definition run fails because validation of the CRM Analytics Dataflow jobs for Data Sync fails. | DATA_SYNC_ERROR_VALIDATION_FAILURE | |
| A definition run fails because a concurrent CRM Analytics Dataflow using the same data sources causes a row lock conflict. | DATA_SYNC_ERROR_ROW_LOCK_NO_EXCLUSIVE_ACCESS | Schedule the definition and the conflicting CRM Analytics Dataflow so they don't run at the same time. |
| A definition run fails because one or more data source objects are also used by a CRM Analytics Dataflow running in parallel. | DATA_SYNC_ERROR_EXCLUSIVE_ACCESS_NOT_OBTAINED | Schedule the definition and the conflicting CRM Analytics Dataflow so they don't run at the same time. |
| A definition run fails because the Data Sync job was terminated due to inactivity. | DATA_SYNC_ERROR_JOB_KILLED_DUE_TO_INACTIVITY | Run the definition again. If the issue persists, contact Salesforce Support. |
| A definition run fails because the latest sync of an object contains new and changed records that are cumulatively more than 900 MB. | None | Create a full sync in Data Manager for the object, then run the definition again. If the object is regularly updated with large volumes of data, sync your data frequently to prevent future failures. For more information about why data syncs fail at this size, see Data Sync Jobs Fail with "InternalServerError: Retried more than 30 times". |
| A definition run fails because one or more fields aren't available in your Salesforce org and can't be replicated. | None | Remove the unavailable fields from the Connections tab:
|
| A definition run fails because a data flow instance is canceled and DPE can't process the data in the source object. | None | Disconnect the data source and run the definition again:
|
| A definition run processes no records. | None | The source object of the definition may not be added as a connection in Data Manager. When a definition runs, it automatically adds connections for all source objects and syncs them. If source objects aren't added automatically, add them manually in the local Salesforce connection in Data Manager. For more information, see Add and Remove Local Salesforce Objects and Fields from Data Sync. |
| A definition run fails because one or more fields selected in a source node don't exist and can't be processed. | None | This issue occurs when related object fields are selected in a source node but aliases aren't specified for the selected source object fields. Specify aliases for all selected source object fields, then run the definition again. |
Troubleshoot Data Transformation Errors for Data Processing Engine Runs
A Data Processing Engine definition run can fail when the runtime platform fails to transform data based on the definition's node configurations. Learn how to resolve data transformation issues for definition runs.
Identifying Data Transformation Issues
Identify definition runs where data transformation failed by verifying one of these in the run's batch job in Monitor Workflow Services:
- The execution status of the run is set to Execution on the Details tab.
- The status of the Execution batch job part is set to Failed on the Tasks tab.
Fixes for Data Transformation Errors for CRM Analytics Runtime
| Issue | Error Code | Resolution |
|---|---|---|
| A definition run fails because the CRM Analytics recipe responsible for data transformation fails during execution. | RECIPE_EXECUTION_ERROR | Run the definition again. If the issue persists, contact Salesforce Support. |
| A definition run fails because DPE can't create the CRM Analytics recipe. | RECIPE_EXECUTION_ERROR_POST_CALL | |
| A definition run fails because DPE can't retrieve the CRM Analytics Dataflow job details needed for writeback. | RECIPE_EXECUTION_ERROR_DATAFLOW_JOB_FAILURE | |
| A definition run fails because DPE can't retrieve the CRM Analytics Dataflow instance ID, which prevents writeback. | RECIPE_EXECUTION_ERROR_DATAFLOW_INSTANCE_ID_NULL | |
| A definition run fails because the CRM Analytics recipe fails the validation phase before data transformation. | RECIPE_EXECUTION_ERROR_VALIDATION | |
| A definition run fails because DPE can't delete the auto-generated CRM Analytics recipe after transformation completes. | RECIPE_EXECUTION_ERROR_DELETED | |
| A definition run fails because DPE can't retrieve the Dataflow job status by recipe label. | RECIPE_EXECUTION_ERROR_DATAFLOW_JOB_STATUS_BY_RECIPE_LABEL | |
| A definition run fails because a user manually canceled the CRM Analytics recipe while the definition was running. | RECIPE_EXECUTION_ERROR_CANCELED | Run the definition again. Don't cancel the CRM Analytics recipe while the definition is running. |
| A definition run fails because a user manually stopped the Data Sync job. | RECIPE_EXECUTION_JOB_KILLED_BY_USER | Run the definition again. Don't stop the Data Sync job while the definition is running. |
| A definition run fails because the recipe execution job was terminated due to inactivity. | RECIPE_EXECUTION_ERROR_JOB_KILLED_DUE_TO_INACTIVITY | Run the definition again. If the issue persists, contact Salesforce Support and ask them to increase the memory factor for CRM Analytics recipes. |
| A definition run fails because DPE can't create the CRM Analytics recipe that transforms data for the run. | RECIPE_EXECUTION_USER_ERROR | Run the definition again. If the issue persists, contact Salesforce Support. |
| A definition run returns errors for formulas that use picklist fields. | None | This issue can occur when a formula uses a picklist field where the combined character count of all picklist values is more than 4,000 characters. To make sure formulas work for large picklist fields, either add a Filter node before the Formula node to remove picklist values that aren't required in the formula, or create a Formula node for each picklist value. |
Troubleshoot Data Writeback Errors for Data Processing Engine Runs
A Data Processing Engine definition run can fail when the definition tries to write back results to the target objects. To check why a particular writeback task failed, use the Get Job Failed Record Results API. In the API URI, specify the failed task job's reference ID as the job ID.
Fixes for Data Writeback Errors for CRM Analytics Runtime
| Issue | Error Code | Resolution |
|---|---|---|
| A definition run fails because DPE encounters a generic error during writeback. | DPE_ERROR_WRITEBACK_FAILURE | Run the definition again. If the issue persists, contact Salesforce Support. |
| A definition run fails because DPE can't read the transformed data required for writeback. | DPE_ERROR_WRITEBACK_DATA_READ_FAILURE | |
| A definition run fails because the data fails writeback validation before DPE writes it to the target objects. | DPE_ERROR_WRITEBACK_VALIDATION_FAILURE | |
| A definition run fails because CRM Analytics doesn't return the required batch job parts for writeback. | DPE_ERROR_WRITEBACK_NO_EXPORTED_BATCH_JOB_PARTS | |
| A definition run fails because of an error in the Composite Writeback node. | DPE_ERROR_COMPOSITE_WRITEBACK_FAILURE | |
| A definition run fails because a Composite Writeback node encounters an unrecognized or unsupported writeback operation. | COMPOSITE_WRITEBACK_UNKNOWN_OPERATION_ERROR | |
| A definition run fails because a required CSV column is missing from the data exported by a Composite Writeback node. | COMPOSITE_WRITEBACK_ERROR_CSV_COLUMN_NOT_FOUND | |
| A definition run fails because a Composite Writeback node has no data to write back. | COMPOSITE_WRITEBACK_NO_EXPORTED_PARTS_ERROR | |
| A definition run fails because DPE can't calculate the count of records to write back. | DPE_ERROR_OUTPUT_COUNT_FAILURE | |
| A definition run fails because the Bulk API 2.0 job creation request for writeback fails after retries. | None | Contact Salesforce Support. |
| A definition run fails because the Bulk API 2.0 execution for writeback fails. | None | Make sure the org hasn't reached its Bulk API 2.0 ingestion limit of 150 million records in a 24-hour rolling period. If the limit has been reached, schedule the definition's run during a low-activity period. |
| A definition run completes, but returns incorrect currency values in the written-back results. | None | During data sync, all currency field values are converted to the org's default currency. Assign the currency you want to write back as the personal currency for the integration user, the writeback user, and the Salesforce admin assigned the Data Pipelines Base User permission set. |
| A definition run completes, but the written-back results are incorrect because source records were only partially synced. | None | This issue occurs when the latest records from one or more source objects fail to fully sync in CRM Analytics. Data sync jobs can fail or complete with warnings. Sync the objects manually in CRM Analytics and verify that each job completes with the status Successful. After a run completes and the batch job parts for data sync are in the Completed status, incorrect results can still occur if CRM Analytics only partially synced the source records with warnings. See Run Data Sync Manually. |
Troubleshoot Runtime Platform Utilization Errors for Data Processing Engine Runs
A Data Processing Engine definition run can fail when the org reaches its provisioned Data Pipelines limits. Learn how to resolve runtime platform utilization errors for definition runs.
Fixes for Runtime Platform Utilization Errors for CRM Analytics Runtime
| Issue | Error Code | Resolution |
|---|---|---|
| A definition run fails because the org has exhausted its hourly Data Pipelines limit for recipe job runtime. | RECIPE_EXECUTION_ERROR_RUNTIME_LIMIT_REACHED | Contact your Salesforce account executive to purchase Data Pipelines add-ons. After the limit resets, run the definition again. |
| A definition run fails because the org has exhausted its monthly Data Pipelines limit for recipe rows out. | RECIPE_EXECUTION_ERROR_ROW_OUT_LIMIT_REACHED | Contact your Salesforce account executive to purchase Data Pipelines add-ons. After the limit resets, run the definition again. |
| A definition run fails because the org has exceeded the total dataset row limit across all datasets. | RECIPE_EXECUTION_ERROR_DATASET_ROW_LIMIT_REACHED | Go to the Usage tab in Data Manager to review your org's overall dataset row consumption. To stay within your org's row limit:
To increase your org's data limits, contact Salesforce Support. |
Troubleshoot Validation Errors for Data Processing Engine Runs
A Data Processing Engine definition run can fail when the Data Processing Engine tries to validate the input and output of the run's stages. Learn how to resolve validation errors for definition runs.
Fixes for Validation Errors
| Issue | Error Code | Resolution |
|---|---|---|
| A definition run fails because the definition doesn't pass platform validation checks before execution. | USER_ERROR_DEFINITION_VALIDATED_FAILURE | Review the definition configuration in the Builder, fix any validation errors, then run the definition again. |
Troubleshoot Other Errors for Data Processing Engine Runs
A Data Processing Engine definition run can fail due to errors where the root cause isn't available. Learn how to resolve definition run errors where the reason is unknown.
Fixes for Other Errors
| Issue | Error Code | Resolution |
|---|---|---|
| A definition run fails because DPE can't queue the run. | ENQUEUE_ERROR | Run the definition again. If the issue persists, contact Salesforce Support. |
| A definition run fails because the run times out before it can start. | TIMEOUT_ERROR | |
| A definition run fails because the runtime platform is set to On Demand but the run was triggered on the CRM Analytics or Data 360 platform. | ONDEMAND_EXECUTION_ERROR_UNSUPPORTED | Change the runtime platform of the definition to match how you run it, or run the definition on demand. |
| A definition run fails because DPE can't retrieve the definition details before starting transformation. | DPE_ERROR_GET_DEFINITION_FAILURE | Run the definition again. If the issue persists, contact Salesforce Support. |
| A definition run fails because of an unexpected error. | DPE_ERROR_UNKNOWN_FAILURE | |
| A definition run fails because data replication in CRM Analytics isn't enabled. | None | An issue with Data Pipelines in your org can prevent replication from being enabled. Turn off Data Pipelines, and turn it on again. |
| A package deployment fails because the package contains Data Processing Engine definitions that reference custom objects. | None | Add the custom objects to the target org by using a separate package. Then add the definition to the target org by using another package. |
| A definition run fails because the system can't enqueue a message for Composite Writeback processing. | COMPOSITE_WRITEBACK_ENQUEUE_ERROR | Run the definition again. If the issue persists, contact Salesforce Support. |
| A definition run fails because the system can't enqueue a message for retry writeback processing. | SCALED_WRITEBACK_ENQUEUE_ERROR |
Эта статья решила вашу проблему?
Оставьте свой отзыв, чтобы мы могли стать лучше!
