How do I migrate to the new SLA functionality (Hold Until) without impacting pending records in my Time-Based node?
The new SLA functionality is more robust and efficient than Time-Based. Read more about the functionality and benefits here.
To get started on the updates, please review your existing Time-Based nodes.
If none of your Time-Based nodes have conditions with the has changed or has not changed operator, please do the following:
- Ensure a Hold Until node with the exact same name as your Time-Based node exists in the new graph (node names are case sensitive)
- Add a decision node following the Time Expired edge with your conditions previously captured in the Time-Based node AND
- Do not add has changed conditions
If any of your Time-Based nodes have conditions with the has changed or has not changed operator, you will need to do the following to prevent LeanData from canceling the hold on the pending records.
- Replicate the has changed operator and condition exactly as they are in Time-Based for the Hold Until node
- Do not add new has changed conditions AND
- Ensure the Hold Until node name matches the Time-Based node name (node names are case sensitive)
After you deploy your graph following the steps above, you should see the following behavior:
- The Time-Based held records will exit the node once their original expiration time is up.
- For example, if they had 20 minutes remaining prior to re-evaluation, LeanData will remember this information, even though you’ve deployed a new graph.
- The Time-Based held records will always exit through the Time Expired edge (regardless of the conditions met.) We recommend adding a Decision node to evaluate the conditions after the record exits the node.