Expand my Community achievements bar.

Never miss an update of the Adobe Journey Optimizer Community Lens! Subscribe now to get the latest updates, insights, and highlights delivered straight to your inbox every time a new edition drops.

How to do a email retry next day if it's stopped due to capping

Avatar

Level 3

Hi Team, I have created a test journey for a PoC to test a scenario where email 1 is being sent to a customer but due to capping rules (channel/frequency capping) the email doesn't get sent as for the user the quota of emails for the day is already exhausted.

How can I re send the email again tomorrow ? 

I'll have to create a logic to check whether the profile received the email 1 or not, but how to check that in condition ?

I can't use the action id of the node because the person must have passed through that node even after the capping rule.

Check the image attached for reference.

3 Replies

Avatar

Level 3

Hi @DavidKangni , @Mohan_Dugganab , @SatheeskannaK  Can anyone help me with this ?

Avatar

Community Advisor

@HardikJa3

When using daily frequency capping, the cap resets at 00:00:00 UTC each day, as the cap is valid until 23:59:59 UTC. From documentation,

https://experienceleague.adobe.com/en/docs/journey-optimizer/using/conflict-prioritization/capping-r...

"Daily - The daily frequency cap is valid for the day until 23:59:59 UTC and resets to 0 at the start of the next day."

Frequency capping is applied during the email delivery preparation phase, and the exclusion reason is recorded on the profile level. To re-attempt sending the email, you can create an audience that excludes profiles with the specific exclusion reason code and retry the send after a day.

For details on exclusion reason codes, refer to the following documentation:
https://experienceleague.adobe.com/en/docs/journey-optimizer/using/reporting/channel-report/exclusio...

Screenshot 2025-11-17 at 8.53.29 AM.png

Thanks, Sathees

Avatar

Community Advisor

@HardikJa3 

 

the capping for frequency is reset daily and is available at profile level or in the message feedback dataset as the exclusion happens at the message authoring level.

 

your logic of wait an hour may not work because of the latency and time of evaluation vs send but you need to create a batch audience and extend your wait to a day (instead of an hour)

 

Thanks,

David



David Kangni