How can i trigger a recalculation of my Cadence Plan?
There are 2 ways to do this.
A. Update the state of the cadence plan
The state of the Cadence Plan is available from the CALC_STATE table.
-1 Undefined
0 New
2 Calc requested
3 Full calc requested
4 Calc waiting
5 Full calc waiting
6 Calc stopped
7 Calc busy
8 Full calc busy
9 Calc done
10 Calc error
12 Calc cancelled
You need to update the state to 3, which means a full calculation is requested.
UPDATE CLASHPLANS SET CALC_STATE=3 WHERE ID=?
Next restart the campaignagent. The state will be updated to 7.
B. Update the setting CLASHPLANS.AUTORECALC_DT
Another way to do this is by setting the CLASHPLANS.AUTORECALC_DT field to GETDATE(). This will do exactly the same as happens during the automatic recalculation which is configurable on the Cadence Plan. This means:
- The Campaignagent will pick this up.
- The Campaignagent will evaluate which journeys are part of this Cadence Plan and will evaluate all their SQL constraints.
- The Cadence Plan is set to state 3
- Then, the clashagent will pick up the Cadence Plan, setting it to state 8, and will start performing a full recalculation. As this includes re-evaluating all audiences, this indeed takes some time.
- Eventually, when done, the Cadence Plan ends up in state 9.
What happens to contacts that are excluded from receiving an email by the Cadence Plan?
If we relaunch a journey previously executed, will the contacts excluded by Cadence Plan be relaunched or definitively excluded from this journey?
If a contact is excluded from a mailing by a Cadence Plan, this certainly does not mean that this contact will also be excluded from future mailings from the same journey.
Cadence Plans are typically configured to be recalculated overnight. So, if a contact was excluded today, then tonight the Cadence system will evaluate again whether or not this contact is eligible to receive your mailing while still adhering to the rules you created in your plan.
This happens of course, for as long as a journey is actively 'on the planning'. Do note that to make use of such reserved sending slots, the journey does have to be executed.
An example:
A Cadence Plan is configured to allow one mail per day. Several journeys are added to this Cadence Plan, among which one (journey J1) that is 'on the planning' from Monday until Friday.
On Monday, journey J1 executes. Say, a contact X has been excluded because they would be receiving a higher priority mailing. This contact, then, will not receive this mail.
Overnight, the Cadence Plan is recalculated. This journey is still on the planning and, say, cadence decides that user X will now be eligible to receive this mail from J1, because no higher priority journeys exist on this day anymore.
On Tuesday, if J1 executes, user X will receive his mail.
However, if J1 does not execute on Tuesday (for whatever reason), but another lower priority journey J2 did execute, then user X would still not receive any mail at all, because a sending slot had already been reserved for journey J1.
What is a partial vs complete recalculation of a plan?
A partial recalculation is focused on a single journey and is triggered when there is a potential change in target for a journey. This is triggered by the following:
- In Campaign:
- adding a new journey
- saving a journey that has a change in filters or segments
- In Engage:
- adding a new journey
- on every save of a journey
A partial recalculation exists of the following calculations:
- The agent will re-evaluate the target for the specific journey
- The clash matrix section that is related to this journey will be recreated
- All clash segments will be recalculated (not Engage segments)
A full recalculation calculates the complete target for every journey in the clashplan.
This gets triggered when:
- Updating the calculation settings of a Cadence Plan (channels, rules)
- The automatic daily schedule based on the configuration of your Cadence Plan runs
- Clicking the Calculate button on top of the screen
What journeys are not supported in a Cadence Plan?
This information is already available in the Cadence topics in a distributed way, but let's consolidate:
- Journeys containing a Control Group Component
- Journeys containing a Dynamic Split Component
- Campaign journeys containing interfaces such as SMS and Mobile Push. These interfaces do not have a record in the Action queue and cannot be included
- Campaign journeys with exports
- Complex Campaign journeys with many interactions
- Engage Journeys with instant Custom Events
- Engage Journeys containing the Delivery Optimization Component with Experiment option activated.
What journeys should not be added to a Cadence Plan?
- One-off promotions that need to be sent anyway
- Recurring scheduled journeys such as Birthday campaigns
- Transactional journeys such a purchase confirmation
- Triggered journeys that respond to a contact's action
- Journeys in which scheduled messages are behind an event such as 'onNotDelivered' or 'OnScheduled'. These depend on certain events to take place first so when the Cadence Plan is calculated, the exact audience is not known yet
- Custom Journeys with multiple Audience Filter Components because in this case the calculations might become quite tricky
- Custom journeys with Wave Component will not work as expected, especially when the waves are spread over multiple days.
- Custom journeys with Wait Component might not have the expected result as it depends on specific events to take place first.
