I have setup some automation rules using the SLA Breached trigger.
However I am prompted with random failure errors such as the below:
As you an see, this has not been triggered by an issue but is just erroring out on its own.
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.
Thanks for you reply.
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.
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...
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