This capability is rolling out now and will be generally available in the next 4-8 weeks. For more information on how it works see the Community Article or Support Docs.

Hello,

We try to automate the Jira and Confluence backup using webhook calls to the API on a scheduled base. However the real trigerring is not always exactly the configured value depending on the current load of the cloud automations and if the webhook was sent too late one day, the call will fail the next day days because of a few minutes or even seconds not matching the rate limitation of the API.
I'd like to have the ability to retry the call in case the fisrt one failled.

For people who want to roll up metrics and other details for reporting, Automation is pretty much the only choice on Cloud (RIP scripted fields). This makes it kind of important that those rules run as scheduled.

It's very frustrating to debug a report only to find the root cause is some bad data created by a rule that just...didn't work.

It is absolutely crucial for us to knwo that automations run in total and not stop somewhere due to rate limiting resulting in the 429 error. We clone about 70 issues each month for our monthly closing of accounting and controlling and this is not stable currently. The effort to find out which issues exactly have not been cloned and to clone them is enormous. Jira automations is not really usable on operations like this in an environment where reliability is crucial.