How to Check Debug Logs for Data Cloud Triggered Flows

[Prerequisites]

1. Tasks before enabling debug logs: Identify the reproduction steps and prepare a minimal reproduction case. Debug logs can produce massive amounts of data. Without narrowing down the scope, cause identification becomes difficult and time-consuming. We recommend excluding unrelated processes.

2. How to enable debug logs: Refer to Data 360: Enabling Debug Logs for Flows Triggered by Data Cloud Platform Event

3. Analyzing debug logs: We ask that the flow creator performs the debug log analysis. Due to security and specification constraints, debug logs are not recorded on our server side. Furthermore, since the logic and expected behavior are based on the customer design, it is difficult for us to fully grasp and investigate. The most reliable way to resolve issues quickly is for the developer who understands the design intent to review the logs. 

[How to Find Debug Logs]

Navigate to [Setup] | Quick Find: "Debug Logs". Look for logs matching:

• User: Automated Process

• Operation: Platform Event Process

• Log Size: At least 5,000 bytes

• Start Time: Around the time of the incident

[Distinguishing between Flow Builder Debug and Debug Logs]

The Flow Builder debug feature is effective for verification during and after flow creation. However, for troubleshooting production environments—such as when a long-running flow suddenly stops—you must check the actual execution debug logs.

Note: We recommend disabling "Debug Logs" before using the Flow Builder debug feature. If enabled, the logs will record both manual business operations and debug sessions, making it difficult to distinguish between them. Furthermore, since record changes in Flow Builder debug mode are automatically rolled back, the logs may show "success" even though no actual data was modified. To avoid confusion caused by this discrepancy, please perform Flow Builder debugging with debug logs disabled.

[Key Analysis Points for Data Cloud Triggered Flow Debug Logs]

Using the sample output below, we will highlight the primary points to check in a Data Cloud Triggered Flow debug log.

◆ Flow Under Investigation

The following log reflects a flow with these specifications:

• Type: Data Cloud Triggered Flow

• Object: Account

• Trigger: Record is created or updated

• Elements: Record Update element, Send Email action

◆ Sample Debug Log Output

65.0

APEX_CODE,FINEST;APEX_PROFILING,FINEST;CALLOUT,FINEST;DATA_ACCESS,FINER;DB,FINEST;NBA,FINE;SYSTEM,FINE;VALIDATION,INFO;VISUALFORCE,FINER;WAVE,FINEST;WORKFLOW,FINER

17:38:31.0 (806153)|USER_INFO|[EXTERNAL]|005Kj00000DKgrU|autoproc@00dkj00000nbapdman|(GMT+09:00) Japan Standard Time (Asia/Tokyo)|GMT+09:00
17:38:31.0 (959501)|EXECUTION_STARTED
17:38:31.0 (1017687)|CODE_UNIT_STARTED|[EXTERNAL]|EntityEventService:DataObjectDataChgEvent
17:38:31.0 (1123047)|EVENT_SERVICE_PUB_BEGIN|EventType:DataObjectDataChgEvent
17:38:31.0 (1265205)|EVENT_SERVICE_PUB_DETAIL|SubscriptionIds:301Kj000003G9wN|UserId:005Kj00000DE9Xv|EventData:[EntityObject of type: DataObjectDataChgEvent, id: 1e5xx00000BULpY]
17:38:31.0 (1281888)|EVENT_SERVICE_PUB_END|EventType:DataObjectDataChgEvent
17:38:31.0 (1448585)|CODE_UNIT_FINISHED|EntityEventService:DataObjectDataChgEvent
17:38:31.0 (1468512)|EXECUTION_FINISHED

👉️  You can verify that the flow with Record ID: 301Kj000003G9wN has successfully subscribed to the DataObjectDataChgEvent

17:38:31.2 (2587974)|USER_INFO|[EXTERNAL]|005Kj00000DKgrU|autoproc@00dkj00000nbapdman|(GMT+09:00) Japan Standard Time (Asia/Tokyo)|GMT+09:00
17:38:31.2 (739064929)|FLOW_CREATE_INTERVIEW_BEGIN|00DKj00000NbAPd|300Kj00000122xc|301Kj000003G9wN
17:38:31.2 (739494475)|FLOW_CREATE_INTERVIEW_END|5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e|【DataCloud】UpdateFlow

👉️ The log confirms the creation of a FLOW INTERVIEW and the issuance of FLOW INTERVIEW ID: 5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e.
A "FLOW INTERVIEW" is a running instance of a flow—a specific execution session generated each time a user or system triggers a flow based on the "Flow Definition" (blueprint) created in Flow Builder. Therefore, if the FLOW INTERVIEW ID is the same, you can conclude that the related processes were executed within the same session. Additionally, the log reveals that the target flow's name is "【Data Cloud】UpdateFlow."

17:38:31.760 (760408811)|USER_INFO|[EXTERNAL]|005Kj00000DE9Xv|trailsignup.eee04be83d9e90@salesforce.com|(GMT+09:00) Japan Standard Time (Asia/Tokyo)|GMT+09:00
17:38:31.760 (760508034)|FLOW_START_INTERVIEWS_BEGIN|1
17:38:31.760 (763592289)|FLOW_START_INTERVIEW_BEGIN|5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e|【DataCloud】UpdateFlow
17:38:31.760 (764174566)|FLOW_START_INTERVIEW_LIMIT_USAGE|SOQL queries: 0 out of 100
17:38:31.760 (764208040)|FLOW_START_INTERVIEW_LIMIT_USAGE|SOQL query rows: 0 out of 50000
17:38:31.760 (764227361)|FLOW_START_INTERVIEW_LIMIT_USAGE|SOSL queries: 0 out of 20
17:38:31.760 (764236877)|FLOW_START_INTERVIEW_LIMIT_USAGE|DML statements: 0 out of 150
17:38:31.760 (764244860)|FLOW_START_INTERVIEW_LIMIT_USAGE|DML rows: 0 out of 10000
17:38:31.760 (764252317)|FLOW_START_INTERVIEW_LIMIT_USAGE|CPU time in ms: 1 out of 15000
17:38:31.760 (764266663)|FLOW_START_INTERVIEW_LIMIT_USAGE|Heap size in bytes: 0 out of 6000000
17:38:31.760 (764274421)|FLOW_START_INTERVIEW_LIMIT_USAGE|Callouts: 0 out of 100
17:38:31.760 (764283241)|FLOW_START_INTERVIEW_LIMIT_USAGE|Email invocations: 0 out of 10
17:38:31.760 (764291100)|FLOW_START_INTERVIEW_LIMIT_USAGE|Future calls: 0 out of 50
17:38:31.760 (764298761)|FLOW_START_INTERVIEW_LIMIT_USAGE|Jobs in queue: 0 out of 50
17:38:31.760 (764306449)|FLOW_START_INTERVIEW_LIMIT_USAGE|Push notifications: 0 out of 10

👉️  As the FLOW INTERVIEW process begins, you can first review the Flow-related LIMITS (Governor Limits). For example, you can see that only 1ms of the 15,000ms CPU time limit was consumed.

17:38:31.760 (764850298)|FLOW_VALUE_ASSIGNMENT|5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e|$Record|{KQ_ParentAccountId__c=null, ssot__ParentAccountId__c=, KQ_BillContactAddressId__c=null, KQ_SalesPhoneId__c=null, ssot__DataSourceObjectId__c=Account, ssot__Id__c=001Kj00002dQ1XfIAK, ssot__LastModifiedDate__c=2025-11-11 08:11:15, ssot__DataSourceId__c=Salesforce_Home, ssot__LastActivityDate__c=null, KQ_Id__c=null, ssot__CreatedDate__c=2025-11-11 08:11:15, ssot__AccountTypeId__c=, ssot__SalesPhoneId__c=001Kj00002dQ1XfIAK, ssot__BillContactAddressId__c=001Kj00002dQ1XfIAK, ssot__Name__c=AAA Corporation, ssot__Description__c=, ssot__Number__c=}

👉️  In the FLOW_VALUE_ASSIGNMENT section, you can check the values of each field stored in the single record within $Record. Data passed from the Data Action linked to the Data Cloud Triggered Flow is stored in $Record. If there are multiple records, a log like the one above is recorded for each. By reviewing this, you can identify which specific record among the data sent to the Data Cloud Triggered Flow was actually referenced. For example, you can see that the ssot__Name__c value for the Account DMO record referenced in this flow is "AAA Corporation."

17:38:31.760 (765048697)|FLOW_ELEMENT_BEGIN|5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e|FlowRecordUpdate|Update
17:38:31.760 (823554683)|FLOW_ELEMENT_DEFERRED|FlowRecordUpdate|Update
17:38:31.760 (823873322)|FLOW_ELEMENT_LIMIT_USAGE|3 ms CPU time, total 4 out of 15000
17:38:31.760 (823907530)|FLOW_ELEMENT_END|5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e|FlowRecordUpdate|Update
17:38:31.760 (824417536)|FLOW_START_INTERVIEW_END|5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e|【DataCloud】UpdateFlow
17:38:31.760 (824807017)|FLOW_BULK_ELEMENT_BEGIN|FlowRecordUpdate|Update
17:38:31.760 (826028001)|LIMIT_USAGE|[EXTERNAL]|FIELDSETS_DESCRIBES|1|100
17:38:31.760 (830068951)|LIMIT_USAGE|[EXTERNAL]|SOQL_ROWS|1|50000
17:38:31.760 (830089674)|LIMIT_USAGE|[EXTERNAL]|SOQL|1|100
17:38:31.760 (830096682)|LIMIT_USAGE|[EXTERNAL]|AGGS|1|300
17:38:31.760 (830307932)|FLOW_BULK_ELEMENT_DETAIL|FlowRecordUpdate|Update|1
17:38:31.760 (830333119)|LIMIT_USAGE|[EXTERNAL]|DML|1|150
17:38:31.760 (830340194)|LIMIT_USAGE|[EXTERNAL]|DML_ROWS|1|10000
17:38:31.840 (840691333)|CODE_UNIT_STARTED|[EXTERNAL]|DuplicateDetector
17:38:31.840 (840723094)|DUPLICATE_DETECTION_BEGIN
17:38:31.840 (841179779)|DUPLICATE_DETECTION_RULE_INVOCATION|DuplicateRuleId:0BmKj000002Lum0|DuplicateRuleName:Standard Account Duplicate Rule|DmlType:UPDATE
17:38:31.840 (841263314)|DUPLICATE_DETECTION_END
17:38:31.840 (841270348)|CODE_UNIT_FINISHED|DuplicateDetector
17:38:31.760 (879015309)|FLOW_VALUE_ASSIGNMENT|5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e|Update|true
17:38:31.760 (879346268)|FLOW_BULK_ELEMENT_LIMIT_USAGE|1 SOQL queries, total 1 out of 100
17:38:31.760 (879366942)|FLOW_BULK_ELEMENT_LIMIT_USAGE|1 SOQL query rows, total 1 out of 50000
17:38:31.760 (879379727)|FLOW_BULK_ELEMENT_LIMIT_USAGE|1 DML statements, total 1 out of 150
17:38:31.760 (879389712)|FLOW_BULK_ELEMENT_LIMIT_USAGE|1 DML rows, total 1 out of 10000
17:38:31.760 (879398609)|FLOW_BULK_ELEMENT_LIMIT_USAGE|8 ms CPU time, total 12 out of 15000
17:38:31.760 (879546129)|FLOW_BULK_ELEMENT_END|FlowRecordUpdate|Update|1|54

👉️  Execution of the record update element named "Update" is confirmed, along with the fact that one row was updated. For descriptions of elements such as FlowRecordUpdate, please also refer to the Flow pages in the Developer Guide.

17:38:31.760 (879627560)|FLOW_ELEMENT_BEGIN|5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e|FlowActionCall|MailToTest
17:38:31.760 (879660033)|FLOW_ELEMENT_DEFERRED|FlowActionCall|MailToTest
17:38:31.760 (879700419)|FLOW_ELEMENT_LIMIT_USAGE|1 ms CPU time, total 13 out of 15000
17:38:31.760 (879714233)|FLOW_ELEMENT_END|5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e|FlowActionCall|MailToTest
17:38:31.760 (879772086)|FLOW_BULK_ELEMENT_BEGIN|FlowActionCall|MailToTest
17:38:31.760 (892863633)|WF_EMAIL_SENT|Reference:emailSimple|Recipients:test@salesforce.com |CcEmails:
17:38:31.760 (893360020)|FLOW_ACTIONCALL_DETAIL|5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e|MailToTest|Send Email|emailSimple@2.0.1@2.0.1|true|
17:38:31.760 (893444368)|FLOW_VALUE_ASSIGNMENT|5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e|MailToTest|true
17:38:31.760 (893487749)|FLOW_ACTIONCALL_DETAIL|5543ded13cad479f1ca554c5cffe19a71c3b2d-ea8e|MailToTest|Send Email|emailSimple@2.0.1|true|
17:38:31.760 (893683107)|FLOW_BULK_ELEMENT_LIMIT_USAGE|10 ms CPU time, total 23 out of 15000
17:38:31.760 (893710826)|FLOW_BULK_ELEMENT_END|FlowActionCall|MailToTest|0|13
17:38:31.760 (893995114)|FLOW_START_INTERVIEWS_END|1

👉️  The log verifies that the email transition action named "MailToTest" was executed and that the email was successfully sent to test@salesforce.com.