in whicch cases we use continuous delivery and in wich cases we use recurring delivery?
Hi @Shruti1 ,
If you use continuous delivery and start the workflow, Single delivery will be created and it will add Delivery logs and Tracking logs on to that same delivery each time that the activity executes. So if your workflows run several times a day (for example, for every 15 minutes), best is to use a continuous delivery.
If you use a recurring delivery, each time the delivery activity executes, a new delivery will be created for each execution. For example, if your workflow runs once a day, after a week, 7 deliveries will be created. Each delivery of this will be having its own tracking log. So depends on your use case and reporting, you can choose the type of delivery.
In order ot be more precise: you can use recurring deliveries in the case of Campaign module
Out of the Campaign module, you can use continuous deliveries
As for history, continuous delivery feature was created first and the main feature was to be able to have a type of delivery that can aggregate reports & figures on a triggered event.
the basic example is the "birthday delivery": customers wanted to have one single report instead of 365
Unfortunately continuous delivery should NEVER be employed in the case of campaign module as it is hardly release "operationMgt's token"
Recurring delivery feature has then be created in order to aggregate reports in a same operation.
This is not because you have campaign module installed that you HAVE to use recurring deliveries... Just be sure to use continuous deliveries OUTSIDE operations 🙂