Saving and Cloning of Scenarios

It is recommended to save your work in Bloomreach Engagement app regularly and frequently. This is valid for scenarios as well. It is strongly recommended to save scenarios often, particularly after important and complicated changes to avoid loosing work.

Scenario Usage Warnings

To optimize your campaign's structure, the Scenarios check and inform you about potential usage issues. Results (and possible warnings) of these checks are shown as a warning message in the sidebar of the TEST tab or in the “Confirm scenario execution” modal window when starting a campaign.

Currently, the warning messages have a purely informational purpose and should help you identify and resolve any usage issues that might negatively influence the performance of the given scenario(s) and/or all scenarios running in parallel.

Currently implemented usage checks are for the following errors:

(1) Jinja condition error

  • Occurs when a Condition node containing jinja in some of its filter’s conditions processes more than 100K customers in one run. This can be detrimental to the performance of the whole instance’s campaign structure.
  • Results in a warning message: "Too many customers 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 - i.e., almost every customer might have a different final filter."

(2) Set property node error

  • Occurs when the sum of customers entering all the Set attribute nodes of a campaign exceeds 1 million.
  • Results in a 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."

(3) Dynamic wait node error

  • Occurs when a Wait node with a Dynamic time period parameter (containing jinja) is processing more than 200K customers.
  • Results in a 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."

Save Scenario as a Copy

Function "Save as new" enables making a duplicate of the current scenario. It is used also when overwriting of the original version of the scenario is not desired. Saving scenario as new will create a completely new scenario with new campaign ID but with the same nodes, settings and scenario flow.

Cloning of Scenarios to Other Projects

See "Cloning" section.