Issue Summary

Insight automations with recursion has unpredictable behaviour

Steps to Reproduce

1. Create an automation triggered by object update
2. Include a groovy script that will update an object that can trigger the automation itself
3. Manually update an update so that the automation is run
4. Look at the Jira log to monitor how the automation behaves

Expected Results

This is a design choice, but at least it should be consistent. Do we allow it to keep calling itself or should a fail-safe be built in?
Furthermore, if attribute an attribute is updated on the object, the next script-call should use that updated value and not the old one.

Actual Results

In the words of the user:

1. If a Groovy script is fired due to the update of, say,  object XY-123 and that script then makes 4 updates to attributes on XY-123, it is unpredictable how many times the script will be called again.  It can be anything from zero times to four times.

2. Related to the prior issue, if the script is called again, the object passed to the script does NOT reflect all updates.  For example, if the script is called again twice I often see this strange outcome: Call #1 – the script is passed an object with only 3 of the 4 changes included; Call #2 – the script is passed an object with only 2 of the 4 changes included.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available