Understanding the Dependency

The Create Consent action itself does not depend on the Data Graph or the Unified Individual, but the use of Data Graph merge fields in the email can trigger the 24-hour wait requirement. This is because the Data Graph and Unified Individual may not exist yet at the time of the form submission, hence the mandatory wait.

The root cause of this issue is often the use of Data Graph merge fields in the email or the presence of old merge field references to the Data Graph, which can be sticky and trigger the 24-hour wait requirement.

To resolve this issue, it is recommended to start from scratch and create a new email without copying any existing emails that may contain Data Graph merge fields. Alternatively, you can try switching the Data Graph, deleting the affected component or section, and redoing only that part with the event fields.

Step-by-Step Solution

Here is a step-by-step guide to resolving the 24-hour wait requirement in Marketing Cloud Next event-triggered flows:

Marketing Cloud Next Event-Triggered Flow

Create/update Contact/Lead
Create/update Campaign Member
(Optionally) create Consent
Wait 24h
Send Email

Heads up: Make sure to test your email and flow thoroughly to ensure that the 24-hour wait requirement is resolved and the email is sent immediately.

Checklist

Resolving the 24-Hour Wait Requirement

• Check if the email references any Data Graph merge fields
• Try starting from scratch and creating a new email without copying any existing emails
• Switch the Data Graph and delete the affected component or section
• Redo only the part with the event fields
• Test the email and flow thoroughly to ensure the 24-hour wait requirement is resolved
• Verify that the Create Consent action does not depend on the Data Graph or Unified Individual
• Check for any old merge field references to the Data Graph that may be triggering the 24-hour wait requirement

Frequently Asked Questions

What triggers the 24-hour wait requirement in Marketing Cloud Next event-triggered flows?

The 24-hour wait requirement is often triggered by the Send Email Message Activity or by the use of Data Graph merge fields in the email.

Can I move the 24-hour wait further down in the flow?

Yes, it is possible to move the 24-hour wait further down in the flow, but only if the email does not reference any Data Graph fields.

How do I resolve the 24-hour wait requirement in Marketing Cloud Next event-triggered flows?

To resolve this issue, start from scratch and create a new email without copying any existing emails, or try switching the Data Graph and deleting the affected component or section.

What is the root cause of the 24-hour wait requirement?

The root cause of this issue is often the use of Data Graph merge fields in the email or the presence of old merge field references to the Data Graph, which can be sticky and trigger the 24-hour wait requirement.

How do I test my email and flow to ensure the 24-hour wait requirement is resolved?

Test your email and flow thoroughly to ensure that the 24-hour wait requirement is resolved and the email is sent immediately.