-
Bug
-
Resolution: Fixed
-
Medium
-
10
-
Severity 3 - Minor
-
6
-
Issue Summary
We are facing racing conditions when multiple automation rules are running in parallel which are attempting to update an object.
Steps to Reproduce
- Create 5 automations in parallel(with object created trigger) which are suppose to update 5 user attribute using email address.
- Import ~1500 objects using a CSV file
- Automation will work for the most part but will fail 10% of the time
Expected Results
Objects should be updated successfully
Actual Results
Few objects are failing to update due to race condition and automation is failing with error:
Error updating Object
Workaround
Trigger: Scheduled
Branch: AQL targeting user attribute value missing
Action: Send web request -
https://<your-jira-tenant>.atlassian.net/rest/api/3/user/search?query={{Object.Email}}
Action: Edit Object - Select the attribute field -
{{webResponse.body.accountId}}
Note: Below options should be enabled in send web request action
- Delay execution of subsequent rule actions until we've received a response for this web request
- Continue running the rule even if the request response is not successful (i.e. non-200 response)
- is related to
-
JSDCLOUD-15164 Assets Object Updated Trigger Smart Values: When a series of rapid updates occur, the smart value for the object returns object information for when the rule runs rather than when the rule is triggered.
-
- Gathering Impact
-