Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-15090

Assets Automation - Enabling "triggered by another automation rule" on Object Updated trigger can lead to loop executions

XMLWordPrintable

      Issue Summary

      The Object trigger which is set to Updated objects can run in loops when allowed other rule actions to trigger this rule. 

      Steps to Reproduce

      1. Add Object Updated trigger
      2. Add action to update the object attribute to static value (i.e text attribute "1")
      3. In Rule details check the flag "allow other rule actions to trigger this rule"
      4. Update any attribute on the object

      Expected Results

      Rule will update object one or two times and detect loop and stop

      Actual Results

      Rule will be running in loops trying to update the object.

      Workaround

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

          Form Name

            [JSDCLOUD-15090] Assets Automation - Enabling "triggered by another automation rule" on Object Updated trigger can lead to loop executions

            marcos.ferreira2 added a comment -

            My team also experienced this issue.

            marcos.ferreira2 added a comment - My team also experienced this issue.

            Erik Furset Jensen added a comment -

            My team and I ran into this bug, we had an automation which updated a object when a new user is added. In the start of the automation (past the conditions) we had a date attribute we updated to "now", and then the rest of the automation actions. We had to solve this by removing the update attribute action to prevent the loop from happening.

            Hope this helps someone in the future

            Erik Furset Jensen added a comment - My team and I ran into this bug, we had an automation which updated a object when a new user is added. In the start of the automation (past the conditions) we had a date attribute we updated to " now ", and then the rest of the automation actions. We had to solve this by removing the update attribute action to prevent the loop from happening. Hope this helps someone in the future

              Unassigned Unassigned
              207d30156835 Ivan Chapistrak
              Affected customers:
              9 This affects my team
              Watchers:
              9 Start watching this issue

                Created:
                Updated: