Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Intermittent error concerning SLA Breached automation


I have setup some automation rules using the SLA Breached trigger.

However I am prompted with random failure errors such as the below:

SLA Breached error.png

As you an see, this has not been triggered by an issue but is just erroring out on its own.

Any ideas?



1 answer

0 votes
Jack Community Leader Jun 08, 2021

The error message is odd. And I wonder what your automation looks like. Could you share a screenshot? What I don’t understand in the error is you have a custom field that appears to be looking for a value that is less than 1433 minutes and at the same time greater than 1440 minutes which certainly doesn’t make sense.

Hi @Jack 

Thanks for you reply.

The rule:


The custom field which is being checked is the "SLA - Waiting for Customer" which I have created to track the time spent in the "Waiting for Customer" status. It is not a custom field per say but a custom SLA.

The weird part is that this error is being triggered even though the SLA has not been breached. It seems like it's an auto-trigger of the filter itself; since the rule is running correctly for any ticket for which this SLA is breached.



And sometimes for another rule using the same SLA, I'm getting the below error messages and it's very intermittent:


Jack Community Leader Jun 08, 2021

Not sure what the cause may be TBH

Is there some sort of automatic verification of filter on Atlassian side? I am asking since it seems that the system has ran this filter randomly and hence this error message

And as you can see, the rule is running perfectly for when a ticket is breached in a project but this error is for "Global":sla5.png

Jack Community Leader Jun 08, 2021

So do you want this to be a global rule? It seems odd that that would be a global rule. 


Because it applies to all my projects....

And like I mentioned, it is an SLA which provides a countdown for when a ticket is in "Waiting for Customer" and then is triggered once the threshold is met. 

Jack Community Leader Jun 22, 2021

I might suggest reaching out to Atlassian support - 

Thanks @Jack 

Much appreciated.

Have a nice day ahead

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Service Management

JSM June ask me anything (AMA)

Hello Community members! We’re wrapping up the end of JSM June with an Ask Me Anything (AMA) with the Jira Service Management product team. This is your chance to ask all your ITSM questions to o...

161 views 9 10
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you