-
Type:
Bug
-
Resolution: Won't Do
-
Priority:
High
-
Component/s: Assets - Service, performance, functionality
-
3
-
Severity 3 - Minor
-
4
-
Warranty
Issue Summary
Assets automation triggered duplicate executions after re-arch.
Steps to Reproduce
- Create an automation rule to be triggered by object update
- Use a boolean attribute A1 as condition
- When A1==true, update A1 back to false and do some action, e.g. create Jira ticket
- Go to Assets UI and pick an object
- Make few object update in a short period of time:
- Update a few attributes
- Update A1 to true
Expected Results
The automation rule should be triggered once for each object update, however only one execution should actually create a Jira ticket due to the boolean attribute condition that controls its execution steps.
Actual Results
The automation rule executions suffer a racing condition and more than one execution actually creates the Jira ticket.
Workaround
Only update the condition boolean attribute as the last step from UI.