What does the Prevent multiple automations option for Automations really mean?

Question

We are having an issue with the following error showing up in our exception log: 
 ScriptException: Maximum scripted extension stack depth (10) exceeded. (An unidentified error occurred within a script.) My assumption was that the Prevent Multiple Automations would prevent this form happening, but it did not. How should I resolve this Maximum scripted extension stack depth issue?

Michael Monteleone · Accepted Answer

Interesting. There are a few different approaches you could try. 
 1 - You could try storing some temp data from your automation when it runs somewhere - potentially in an extended attribute on the user, or with the context_v2_automationState Script API to flag that the user's avatar has already been randomized, and so when the automation runs again after updating the avatar, it can check that flag to avoid updating any subsequent times. 
 2 - Instead of updating the avatar directly within the automation, you could schedule a background script execution from the automation with an appropriate delay, and then have the automation run from the user create instead, so that by the time the scheduled avatar change happens, the oauth plugin would no longer have a chance to overwrite. Kind of a hack, but could work. 
 3 - You could potentially update the oAuth plugin to use your randomized avatar instead of whatever it's currently doing on create.

What does the Prevent multiple automations option for Automations really mean?

Top Replies