Asset automation duplicated execution

XMLWordPrintable

    • 3
    • Severity 3 - Minor
    • 4
    • Warranty

      Issue Summary

      Assets automation triggered duplicate executions after re-arch.

      Steps to Reproduce

      1. Create an automation rule to be triggered by object update
      2. Use a boolean attribute A1 as condition
      3. When A1==true, update A1 back to false and do some action, e.g. create Jira ticket
      4. Go to Assets UI and pick an object
      5. Make few object update in a short period of time:
        1. Update a few attributes
        2. 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.

              Assignee:
              Unassigned
              Reporter:
              Kevin Ma
              Votes:
              4 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: