I have a question about the continuous delivery activity.
I understand it can be used so that a workflow can run multiple times, returning different recipient data and send the same delivery template - but when there are multiple executions - it results in all the results being stored under a single delivery (rather than a delivery per execution).
I can see this being ideal for small/regular volumes (like a daily welcome email), but is it also fit for purpose for larger volumes?
Say, up to a total of 1 million? perhaps 50-100 executions over a week period?
I have a campaign that I'd like to execute to a large volume to different segments at lots of different times per segment, and ideally would like it to result in a single delivery - just want to make sure the activity is fit for purpose.
The question was more about size / scale. Is it fit for purpose for large volumes like detailed above?
Should be fine, it's just using one delivery id vs another for more of the same stuff- delivery parts, logs, etc.