Recurring Delivery not triggering post-processing workflow when target is empty | Community
Skip to main content
Heku_
Heku_
December 16, 2024
Solved

Recurring Delivery not triggering post-processing workflow when target is empty

  • December 16, 2024
  • 1 reply
  • 586 views

Hi everyone,

I’m facing an issue with a Recurring Delivery in Adobe Campaign where the post-processing workflow doesn’t get triggered if the target contains 0 records.

Here’s the context:

  • I have two identical deliveries:
    1. One is launched using a Phone Delivery activity, which always triggers the post-processing workflow even if the target is empty. I get this log message:              
    2. The other is launched using a Recurring Delivery activity, which doesn’t trigger the post-processing workflow when the target is empty. Instead, it gets stuck with the log message:

       

This behavior only occurs when the target contains 0 records.

I would like to know:

  1. Why is this difference in behavior happening between Phone Delivery and Recurring Delivery?
  2. How can I ensure that the post-processing workflow is triggered for Recurring Delivery, even when the target is empty?

I need a solution that works without adding extra activities or JavaScript code. Ideally, it should be a configuration adjustment.

Thanks in advance for your help!

Best answer by pankajverma-1

Hi Heku,

 

I’m not certain if there is a specific configuration that governs this behavior for Recurring Deliveries or if such a configuration exists. However, I would suggest using a conditional check (e.g., recCount) before the Recurring Delivery in the workflow. I understand your preference to avoid extra activities, this approach ensures a more controlled and predictable process.

 

If the recCount is 0, you can bypass the Recurring Delivery and directly trigger the post-processing workflow.

 

Thanks,
Pankaj

1 reply

P
Adobe Employee
pankajverma-1Adobe EmployeeAccepted solution
Adobe Employee
January 9, 2025

Hi Heku,

 

I’m not certain if there is a specific configuration that governs this behavior for Recurring Deliveries or if such a configuration exists. However, I would suggest using a conditional check (e.g., recCount) before the Recurring Delivery in the workflow. I understand your preference to avoid extra activities, this approach ensures a more controlled and predictable process.

 

If the recCount is 0, you can bypass the Recurring Delivery and directly trigger the post-processing workflow.

 

Thanks,
Pankaj

    Terms & ConditionsAccessibility statement

    Loading footer...