Flow: MCN to CRM Email Consent Status Update
Trigger: Data Cloud-Triggered Flow on ssot__CommunicationSubscriptionConsent__dlm, "A record is created or updated," 1 entry condition
Logic: Get Lead (matched via IndividualId = ssot__PartyId__c) → Real Change Check (compares Lead's Consent_Sync_Status__c picklist to incoming ssot__PrivacyConsentStatus__c) → if different, update Lead's HasOptedOutOfEmail and Consent_Sync_Status__c.
Debug (manually selecting a Data Cloud record) runs end-to-end successfully and updates the Lead correctly. But updating Consent Status for real in production never triggers the flow — waited 20+ minutes.
Has anyone hit this same Debug-works/real-trigger-doesn't gap on Data Cloud-Triggered Flows? Is it an entry condition prior-value issue, or a DMO ingestion delay?
#MarketingCloudNext
Hi Khushal,
Looking at your screenshot, there is an immediate culprit visible right at the top bar:
1. The Flow Version is Currently Inactive
In your screenshot, the status pill next to the save date clearly shows Inactive, and the blue Activate button is present in the top-right corner.
- In Flow Builder, the Debug button works regardless of whether the flow is active, because it allows you to simulate execution on any saved draft version.
- However, a Data Cloud-Triggered Flow will never listen for or fire on incoming DMO events until it is explicitly Activated.
- Action: Click Activate in the top right, make sure the status pill turns green (Active), and then test again.
If it remains inactive or fails to trigger even after activating, check these three common Data Cloud-specific caveats:
2. Check the Start Element Entry Condition Requirement
In the start element, you have "1 Entry Condition" defined:
- When setting entry criteria with "A record is created or updated", check the evaluation setting: "Only when a record is updated to meet the condition requirements" vs. "Every time a record is updated and meets the condition requirements".
- In Data Cloud, change-data-capture evaluation for previous values can behave unexpectedly if incoming updates from ingestion streams batch or upsert without firing delta states. If possible, set it to evaluate every time or handle the strict filtering inside your decision elements instead.
3. Ingestion & DLO-to-DMO Mapping Cadence
- How is the consent record being updated upstream? If it enters via a Data Stream (e.g., Connector or Ingestion API), it writes to a Data Lake Object (DLO) first.
- The Data Cloud-Triggered Flow listens to the DMO (ssot__CommunicationSubscriptionConsent__dlm), not the DLO. Depending on the ingestion stream type (streaming vs. hourly/batch batch run), there can be a delay between the data entering Data Cloud and the DMO upsert actually publishing the change event that the flow subscribes to.
4. Data Space Mismatch
- Your start element is set to Data Space: default.
- Ensure the incoming consent updates are actually being ingested and resolved into the default Data Space and not routed into a custom Data Space (which would isolate the records from this trigger).
Summary: Hit the blue Activate button first—that is almost certainly why Debug works while real events are completely ignored!
