Track CRM Analytics (CRMA) Data Sync Status of Definition Runs
When you run a definition, the data sync jobs run to extract data from each Salesforce
object that’s selected as a data source. For example, if the definition pulls data from the
Opportunity and Account objects, a separate data sync appears for each object. After the data
syncs are complete, the definition runs. To view the status of data syncs and Data Processing
Engine definitions, use the Monitor tab on Data Manager.
Note During a definition's run, Data Processing Engine replicates source Salesforce object
data into temporary datasets in CRM Analytics so the recipe can process it. These replicated
datasets count toward your org's total dataset row limit, even when the definition writes
results back to a Salesforce object rather than to a dataset. The replicated datasets are
listed as connected data assets named after the source object (for example, Account or
Event) and are accessible from the Connections tab in Data Manager under SFDC_LOCAL. The row
storage limit applies only to input rows when source data is replicated into CRM Analytics.
Output rows written back to a Salesforce object are governed by a separate output limit over
a rolling 24-hour window.
From the App Launcher, find and select Data Manager, and then
click Data Manager.
Monitor the data sync jobs for each Salesforce object that’s selected as a data source.
Monitor the status of the Data Processing Engine definition.
The Data Processing Engine definition runs after the data sync jobs complete. The
Monitor tab shows the definition's run as a Recipe job type. When the run completes, the
recipe is removed from the Monitor tab.
To track the status and details of a definition's run, go to Monitor Workflow
Services.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.