Note: these steps apply to Platform Event Triggered Flows where the Data Object Data Change Event platform event is selected in the Start element and Data 360 Triggered Flows. Both of these autolaunched flow types subscribe to DataObjectDataChgEvent platform events, which are triggered via Data 360 Data Actions when changes occur to records in Data 360 data model objects (DMOs) or calculated insights (CIs).
Creating a Data 360 Triggered Flow in your Data 360 org automatically creates a Salesforce Platform Event Data Action and Data Action Target, which generate events based on the criteria configured in the flow's Start element where the Data Space and Object (i.e. a DMO or CI) are selected and the event conditions are configured.
Note: when activating a second Data 360 Triggered Flow the first Data Action Target is reused and only a new Data Action is added.
For Platform Event Triggered Flows the Data Action and Data Action Target need to be created manually in Data 360 (see Help documentation linked below). During Data Action configuration you will select the Data Space, Object and Action Rules. Whereas Data 360 Triggered Flows can only be configured within the Data 360 org, if you have other CRM orgs connected to your Data 360 org in Data 360 Setup, you can configure Data Actions to send platform events to a connected CRM org wherein a Platform Event Triggered Flow can then be triggered.
To confirm that a flow is being triggered by the DataObjectDataChgEvent platform event you can enable debug logs. See the steps in Add a Trace Flag Entry for the Default Automated Process User to configure debug logs for Data Cloud-triggered flows or platform event-triggered flows running as the default workflow user. Debug logging needs to be enabled in the same org that the flow is running. For Data 360 Triggered Flows it will be the same org that your Data 360 is provisioned to. For Platform Event Triggered Flows it will be the Salesforce Org selected when you configured the Data Action Target.
Configure the Start Date and Expiration Date to include the timeframe where the change will be made in Data 360. If the process that will be making changes to the records in Data 360 can be started manually (e.g. refreshing a Data Stream or publishing a Calculated Insight) you can set this timeframe for the next hours and then start the process in Data 360. Allow the process to complete and then search Debug Logs in the Quick Find in Setup.
If several minutes after the process has completed in Data 360 you are still not seeing any debug logs review the conditions you configured in the Data Action or Data 360 Triggered Flow Start element to ensure these should have been met. For example, if you configured the action to start when records in a DMO are created or updated and then refreshed a data stream that is mapped to the DMO can you confirm that the data in the fields mapped to the DMO is different to what was there before the refresh? If values were changed check the Condition Requirements in the Start element of the Data 360 Triggered Flow or the Data 360 Action rules (if using a Platform Event Triggered Flow) and confirm the changed records will meet these conditions. Check if the conditions are configured to be met Every time a record update meets these conditions or Only the first time a record update meets these conditions. If choosing the second option, the flow is not expected to be triggered if a record has already previous met the conditions. Consider changing that select if you wish for the record to trigger an event every time it is updated.
If you want to see the data being received in the Salesforce Platform Event payload in the debug logs then set the debug levels in New Debug Level to Finer for the Workflow category.
Please refer to How to Check Debug Logs for Data Cloud Triggered Flows for instructions on how to check debug logs.
001731541

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 are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security 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 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.