How long does automation limit reset evaluation typically take?

[Felipe Siqueira]

Aqui está o texto para o fórum:

---

How long does automation limit reset evaluation typically take?

Category: Jira Cloud / Automation

---

Hi everyone,

I'm currently dealing with a critical situation where an automation rule malfunction caused our monthly execution limit to be exceeded (~80k executions in 16 hours due to an infinite loop).

I opened a support ticket (CA-4067730) requesting an evaluation for a counter reset/waiver given that:

• This was a configuration error, not normal usage
• First time this has happened in our account
• The faulty rule is now disabled
• Our business operations are completely blocked without automation capabilities

The support agent transferred my ticket to the "automation limits team" for evaluation over 3 hours ago, but I haven't received any update yet.

My questions for the community:

1. Has anyone gone through a similar automation limit reset request?
2. How long did the evaluation process take in your case?
3. Were you able to get a reset/waiver approved, or is this typically denied?
4. Is there anything I can do to expedite the process?

I understand these things take time, but our entire revenue operation depends on automations being functional, so I'm trying to get a realistic expectation of the timeline.

Any insights from those who've been through this would be greatly appreciated!

Thanks in advance,
Felipe

[Walter Buggenhout · Accepted solution]

Hi @Felipe Siqueira,

You can find Atlassian's official response time SLA's in this support article. You will see these are linked to your subscription plan as well as to the impact / severity level you raised the issue with (Atlassian does review this and adjust if they don't agree).

Hope this helps!  

[Felipe Siqueira]

Hello, @Walter Buggenhout 

We’ve been using the sandbox to build and test our ideas. This time, a small mistake happened while updating a pre-function automation: it was saved without any filter to limit its execution. As a result, the trigger fired every time an issue was updated, creating an infinite loop involving only two issues.

Atlassian Support was very helpful and provided all the instructions I needed to revert the situation. Our limit has been reset, and everything is okay now.

Thank you for the help and guidance. :) 

Best regards,
Felipe

[Joseph Chung Yin · Accepted solution]

 -

Sorry to hear about your situation.  My understanding/experiences from our end was always within one day based on the support case severity level .  In your situation, since it is a production critical, I would recommend you to update the ask to the highest severity level and escalate the ask with Atlassian Support team.

Our high priority asks were always addressed in a timely matters.

Best, Joseph 

[Felipe Siqueira]

Hello,  

We’ve been using the sandbox to build and test our ideas. This time, a small mistake happened while updating a pre-function automation: it was saved without any filter to limit its execution. As a result, the trigger fired every time an issue was updated, creating an infinite loop involving only two issues.

Atlassian Support was very helpful and provided all the instructions I needed to revert the situation. Our limit has been reset, and everything is okay now.

Thank you for the help and guidance. :) 

Best regards,
Felipe

[Arkadiusz Wroblewski · Accepted solution]

Hello @Felipe Siqueira 

Then maybe I can chime in here and add to what my colleague already said.

As a Premium user, you should have access to a sandbox. I am saying this from my own experience, and I learned it the painful way as well.

If an automation could have a bigger impact, test it in the sandbox first. It can save you a lot of stress and sweat in the production system.

Besides that, malfunction or unexpected behavior are something what you can't always ”Overjump" in productive System. We all been there.

[Felipe Siqueira]

Hello,

We’ve been using the sandbox to build and test our ideas. This time, a small mistake happened while updating a pre-function automation: it was saved without any filter to limit its execution. As a result, the trigger fired every time an issue was updated, creating an infinite loop involving only two issues.

Atlassian Support was very helpful and provided all the instructions I needed to revert the situation. Our limit has been reset, and everything is okay now.

Thank you for the help and guidance. :) 

Best regards,
Felipe