Loading
Salesforce now sends email only from verified domains. Read More
Data Processing Engine
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Troubleshoot Data Processing Engine Issues

            You are here:

            1. Salesforce Help
            2. Docs
            3. Data Processing Engine

            Troubleshoot Data Processing Engine Issues

            Can’t seem to get Data Processing Engine working for you? To resolve issues with Data Processing Engine, try these solutions.

            Required Editions

            View supported editions.
            Issue Possible Resolution
            You can't view or write to datasets that were created using the Analytics Cloud Integration User license.

            This issue occurs because you don't have the necessary permissions.

            • From Setup, in the Quick Find box, enter Permission Sets, and then select it.
            • Click New and enter a permission set name. The API name gets autopopulated based on the permission set name.
            • In the License dropdown, select Analytics Cloud Integration User, and save the permission set.
            • On the Permission Sets Overview page, open the permission set that you created, click System Permissions | View All Data, and save the permission set changes.
            • On the Permission Sets Overview page, click Manage Assignments, | Add Assignments, select the user with the Analytics Cloud Integration User profile, click Assign and then click Done.
            You can't open the Data Processing Engine definition if the data source node object doesn't exist.

            This issue occurs when the Salesforce object, dataset, or Data Lake object that's part of the data source is deleted or renamed.

            • Add the Salesforce object or dataset back to the data source node, and try again.
            • Add the Data Lake object with the same name and fields as earlier, and try again.
            Results aren’t written back in the currency of your choice.

            Make sure that the currency that you want to write back the results for is assigned as the personal currency for these users:

            • Integration user
            • Writeback user
            • System administrator assigned the Data Pipelines Base User permission set

            During the data sync process of a definition's run, the values for all the currency fields in the data sources are converted to the org's default currency.
            While reviewing why a definition's run failed, you find errors for formulas that use picklist fields. This issue can occur when a formula uses a picklist field where the combined character count of all picklist values is more than 255 characters. To make sure that that the formulas work for large picklist fields, either use a Filter node before the Formula node to remove any picklist values that aren't required in the formula or create a Formula node for each picklist value.
            While monitoring a definition’s run, you see that the run failed because an object didn't sync. The object successfully synced for previous runs.

            This issue occurs when the object that failed to sync has been synced earlier and the latest sync contains new and changed records that are cumulatively more than 900 MB.

            Create a full sync in the Data Manager for the object, and then run the definition.

            If an object is regularly updated with large volumes of data, sync your data frequently to ensure that your Data Processing Engine runs don't fail.

            To know more about why more than 900 MB can't be synced, see Data Sync Jobs Fail with "InternalServerError : Retried more than 30 times".
            While monitoring a definition’s run, you see that the run couldn't process the data because one or more fields selected in a source node don't exist. 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 the selected source object fields, and then run the definition.
            While monitoring a Data Processing Engine definition’s run, you see that one or more writeback tasks failed. To check why a particular writeback task failed, use the Get Job Failed Record Results API. In the API’s URI, specify the failed task job’s reference ID as the job ID.
            While monitoring a Data Processing Engine definition’s run, you see that the definition didn’t replicate the data for one or more fields.

            The specified fields aren’t available in your Salesforce org. Remove these fields from the Connections tab.

            • Go to Data Manager | Connections.
            • Click the object that contains the fields.
            • Deselect the fields, and click Continue.
            • Save your changes.
            While monitoring a Data Processing Engine definition’s run, you see that a data flow instance is canceled.

            This issue occurs when Data Processing Engine can't process the data in your source object. Disconnect the data source, and run the definition again.

            • Go to Data Manager | Connections.
            • Click dropdown next to the source object.
            • Select Disconnect Object.
            While monitoring a Data Processing Engine definition’s run, you see that replication isn’t enabled. An issue with Data Pipelines in your org can prevent replication from being enabled. Turn off Data Pipelines, and turn it on again.
            While monitoring a Data Processing Engine definition’s run, you see that my org exceeded the data limits. To check if the data limits for your org can be increased, contact your Salesforce representative.
            While deploying a package with Data Processing Engine definitions, the deployment fails. Your definition contains custom objects as data sources or target objects for write-back. Add the custom objects to the target org using a package. Then add the definition to the target org using another package.
            While activating a definition that's created from a template definition, you get an error.

            You don't have access to one or more objects specified as data sources or writeback objects. Verify these requirements:

            • The required Setup objects are enabled. For example, from Setup in Order Settings, the Order object must be enabled.
            • The specified objects are available in your org.
            • You have Read and Create permissions for the objects.
            While monitoring a definition’s run, you see that there were no values for the definition to process. This issue occurs when a source object of the Data Processing Engine definition isn’t added as a connection in Data Manager. When a Data Processing Engine is run, it automatically adds connections for all source objects and syncs them in Data Manager. If the source objects aren’t automatically added as connections in Data Manager, you can add them manually in SFDC_Local. For more information, see Add and Remove Local Salesforce Objects and Fields from Data Sync.
            While reviewing the results that a CRM Analytics runtime Data Processing Engine definition’s run writes back, you see that incorrect results are written back.

            This issue occurs when all the latest records from one or more data source objects of the definition fail to sync in CRM Analytics. Data sync jobs in CRM Analytics can fail or complete with warnings. To make sure the definition processes all the records from objects, sync the objects manually in CRM Analytics and verify that the jobs complete with the status Successful. See Run Data Sync Manually.

            After a definition's run completes and the run's batch job parts for data sync are in the Completed status but the results written back are incorrect, it can be because the definition's data source records were partially synced in CRM Analytics with warnings.
             
            Loading
            Salesforce Help | Article