Uploaded image for project: 'Automation for Cloud'
  1. Automation for Cloud
  2. AUTO-79

Further configuration of automation rules being disabled automatically by Automation For Jira (A4J) - ability to manage retry policy for components or rules

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Problem Definition

      Currently, if there are 10 consecutive failures (5 for SLA related rules) in the execution of an automation rule, then the rule will be automatically disabled by Automation For Jira (A4J). Although notifications are sent for the failed executions, the notifications for the disable action itself is not sent. The automatic disable also cannot be turned off by the admin.

      Suggested Solution

      Allow admins to:

      • receive notification when A4J disables a rule due to the consecutive failures in rules
      • have ability to turn off the behavior of A4J automatically disabling rules
      • At the moment, for "Send Microsoft Teams message" action , it have 30 second to wait for Microsoft Teams to process the action before it hit time out. There are in rare occasion , the action hit 408 error (Request timed out) and automation will failed -> Retry the "Send Microsoft Teams message" action and ensure Microsoft Teams do process the action.
      • Currently in a Jira automation rule, if a "Create issue" action fails due to network timeout (with error: SocketException: Socket closed), the action is not retried. So, issue creation fails.

       

              89403358cf11 Charlie Gavey
              4326607df174 Yuji Sakai (Inactive)
              Votes:
              10 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: