-
Bug
-
Resolution: Fixed
-
High
-
7
-
Severity 3 - Minor
-
7
-
Issue Summary
When updating the different attributes for the same object concurrently, it may lead to race condition intermittently resulting in attributes not saved properly. The scenarios may include:
- In case of manual updating, the object attribute updated and reverted back to it's original value
- Having an automation rule with two or more Edit Object actions updating different attributes, might end up with an object attribute being updated and automatically reverted.
This is reproducible on Data Center: (yes) - It's not always reproducible. It was noticed that we are only able to reproduce it when there are high volume of requests triggering an automation rule that updates the two different attribute at the same time.
Steps to Reproduce
- Create an automation on the object updated event
- Add an action to update at least two attribute one after the other in separate branches
OR
- We can use an API to trigger this behavior:
- Calling this endpoint /automation/objects to update two different attributes for the same object can lead to the race condition. However, each call to the endpoint should update one attribute or the other (not both at the same time).
Expected Results
- The attribute should be updated only once.
Actual Results
- Sometimes we see the attribute being updated twice wrongly or updated and then reverted back to its original value.
Workaround
- This is probably caused due to the simultaneous updation of the attribute. If we are are using an an automation with update attribute action which is updating the different attributes of the same object, then we can introduce delay to avoid getting into the race condition.
- For example:
- For the first brach updating A attribute of object ABC
- Add delay of 5s before the edit attribute action for the first branch
- For the second branch updating B attribute of object ABC
- Add delay of 10s before the edit attribute action for the second branch
- For the first brach updating A attribute of object ABC
Please do not add the delay of same time for all the branches as that may again lead to the race condition.
- has action
-
ANA-3204 Loading...