A Recurring delivery activity lets you configure a delivery template occurrence that is specific to a campaign.
This activity is only available from the Targeting and workflows tab found in a campaign.
To do this:
Select the delivery template that the activity will be based on.
Configure the delivery template.
The configuration process for this activity is similar to that of creating a delivery template in terms of the options available. For more on this, refer to this section.
Recurring deliveries do not support previewing content or sending proofs including target data personalization elements.
For an example of this activity being used, refer to this section.
A recurring delivery will create a new delivery instance each time it executes. For example, if the workflow is scheduled to run once a week, that would result in 52 deliveries after one year. This also means that the broad log and tracking logs will be separated by each delivery instance.
If you want to stop a recurring delivery from running, you should completely cancel the campaign or stop the workflow executing it. Stopping the delivery from the Campaign dashboard will only stop the delivery occurence: the next instances of the recurring delivery will continue being created at each workflow execution.
It is not possible to send a proof from a Recurring delivery type activity.
To directly create a delivery via a campaign workflow, use the channel specific activities that are preconfigured (e.g. Recurring delivery).
This video explains how to configure a recurring delivery and a scheduler activity.
Additional Campaign Classic how-to videos are available here.