Fresh terminology for automation rules and components

An automation ‘rule’ is now a ‘flow', and a ‘component’ is now a 'step’. You may notice some inconsistencies in the documentation while we make this change. Read more about the updates in Automation

Retry failed flows in Atlassian Automation

When a flow is unable to complete a successful run due to a temporary system error, Atlassian Automation may attempt to retry it. When a flow is going to be retried, you’ll see the status Queued for retry in the flow’s audit log entry.

Example of rule queued for retry in Atlassian Automation

When a flow is queued for retry, the step that prevented the flow from completing successfully will be marked with an error icon in the Show more section. You’ll also be able to see a brief description of the error.

Example of specific rule queued for retry in Atlassian Automation

No action is required on your behalf to retry the flow. The system will automatically attempt to run the flow again, from the point of failure, for up to seven days. If the flow is unable to complete a successful run during these seven days, then its status will change to Failure. You’ll also receive a notification that your flow has failed.

Example of failed rule retry in Automation

If the flow completes a successful run when retried, then the flow’s status will change to Success in the audit log. In the Show more section, a retry icon will be displayed next to step(s) which ran successfully after being retried. A brief description of the original error will also be displayed for your reference.

Example of successful rule retry in Automation

Still need help?

The Atlassian Community is here for you.