Retry email excluded by Frequency Capping while preserving journey sequence

Question

Hi, we have a Channel Capping Rule of 1 Email per day shared across multiple journeys.

# Example:

Journey 1
Trigger → Email

Journey 2
Trigger → Email 1 → Wait 1d → Email 2 → Wait 1d → Email 3

Scenario:

Day 1: Journey 2 - Email 1 → SENT
Day 2: Journey 1 - Email → SENT
Journey 2 - Email 2 → EXCLUDED by capping

We need Journey 2 to behave like:

Day 3: Retry Email 2
Day 4: Email 3

The problem is that a capping exclusion does not trigger the Email error path, so the journey continues normally.

We also want to avoid creating one recovery journey or audience per communication because it would not scale.

Is there a more native/scalable Adobe-recommended solution for this use case? Even with Data Distiller is something dificult to achieve.

Thanks.

Pulkit_Jain_ · Answer

​@Silvio6AJO Journey Orchestration does not have a native mechanism to automatically retry a channel step that was skipped due to frequency capping while preserving the remaining journey steps. When a frequency cap exclusion occurs, the profile either continues to the next node or ends with a cappingError end reason — no retry or error path triggering occurs.You can evaluate native workarounds such as journey-internal Wait nodes with re-attempt logic, profile attribute flags with conditional branching, or an automated Data Distiller batch job to identify and retry capped messages.Example- use the built-in "Was sent email" condition node (available on split/condition nodes) — checks if a specific earlier email actually sent.Pattern per journey:Email 2 → (fires or capped)Condition: "Was Email 2 sent?"No → Wait 1d → retry Email 2 → re-checkYes → Wait 1d → Email 3This is a reusable in-canvas template, not an external audience/journey — so it scales.

Sign up

Login with SSO

Login to the community

Login with SSO