Saving and Cloning of Scenarios

Managing scenarios effectively keeps your campaigns running smoothly and protects your work from unexpected issues. This guide shows you how to save, copy, and optimize your scenarios for better performance.

Save your work

Save your scenarios often, especially after making important changes. Regular saving prevents you from losing your work if something goes wrong.

Understand performance warnings

The system automatically checks your scenarios for potential issues that could slow down your campaigns. You'll see warning messages in 2 places:

• The sidebar of the TEST tab.
• The "Confirm scenario execution" window when you start a campaign.

These warnings help you spot and fix issues before they affect the given scenario and/or all scenarios running in parallel.

Fix common performance issues

Too many customers in condition nodes with Jinja

• What happens: A condition node with Jinja code processes more than 100,000 customers in one run.
• Why it's a problem: This can slow down your entire campaign system.
• Warning message: "Too many customers are processed by condition node #1 containing Jinja. Don't use Jinja in condition nodes for processing more than 100K customers in one run if the personalized filters are likely to be highly unique."

Too many set attribute actions

• What happens: All your "Set attribute" nodes combined process more than 1 million customers.
• Why it's a problem: This creates too much database activity.
• Warning message: "Set attribute actions count exceeds the recommended limit. Please, try limiting the "Set attribute" node usage to a maximum of 1M updates in one run."

Too many customers in dynamic wait nodes

• What happens: A wait node with dynamic timing (using Jinja) processes more than 200,000 customers.
• Why it's a problem: Dynamic calculations for large audiences can slow down the system.
• Warning message: "Dynamic wait node #2 is processing too many customers in one run. If possible, consider reducing their count to less than 200K by using filtering conditions before letting them enter the wait node."

Too many nodes in one scenario

• What happens: Your scenario has more than 100 nodes.
• Why it's a problem: Complex scenarios with many nodes can become slow and hard to manage.
• Warning message: "There are too many nodes in this scenario. Consider reducing the number of nodes to fewer than 100 for optimal performance."

Create a copy of your scenario

Use Save as new to create a duplicate of your current scenario. This is useful when you want to:

• Test changes without affecting the original.
• Keep a backup version.
• Create a similar scenario for a different campaign.

The copy gets a new campaign ID but keeps all the same nodes, settings, and flow as the original.

Clone scenarios to other projects

You can clone scenarios to other projects. See "Cloning" section for detailed instructions.

Follow best practices

• Save frequently: Don't wait until you're finished to save your work.
• Fix warnings: Address performance warnings before launching your scenario.
• Test copies: Use "Save as new" to test major changes safely.
• Keep it simple: If you get too many warnings, consider breaking your scenario into smaller, simpler ones.