Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
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

Automation LOOPs issues

Hi, I keep getting "LOOP" status in some of my automations. This leads to sending me emails each time something is in LOOP status.

I tried to read up about it and see whether it's an error, but it isn't clear to me.

I have some automations that run after other automations. Due to the multiple other automations, this specific sometimes doesnt get updated in time, therefore I do RE-FRETCH and since then, i do get this LOOP status issue.

Appreciate your help understand if there is anything I should be doing differently.


1 answer

1 accepted

2 votes
Answer accepted
Alex Koxaras Community Leader Dec 06, 2021

Hi @Meytal BM 🤘

I would be very glad to help you out here, but unfortunately you don't give too much info. I know that you probably have many rules and automation which run on your instance and it will be hard to identify what causes this error. If I were you, I would begin by trying to identify the actions that cause this error. I would also take notes on all rules and automation that run on my project/instance (or between projects). These alone should be able to help you identify the problem.

If you have already identify the problem and it's only a "delay" parameter that should be placed inside an automation, I would then recommend the use of an app, which has a delay function in it.

Thanks @Alex Koxaras and apologies not posting that much info.

Yes, this started when i added re-fetch to specific automation. And as a result, other automations that are "Allow rule trigger" on this specific automation, put these automations in a LOOP status. So am 99% sure this is the issue.

This is just one of the same errors I am getting after i added the re-fetch from another "Allow rule trigger" automation:

Screenshot (38).png

Regarding app, what do u recommend?

Alex Koxaras Community Leader Dec 06, 2021

@Meytal BM 

You have to search deeper into the rules and see why re-fetching the data cause the other rules to be triggered. What kind of trigger do the other rules have?

Concerning the app, I can't recommend anything final yet, till I know what you want to do. You could try JMWE for example, since in many PFs there is the option to delay its execution, as well as to ignore JA automations.

Yeah i hear ya. I am certain this is the issue.

Basically I have multiple automations running when an item is created/updated/value changed. When an issue is created, I send a webhook to an external service, and that service updates specific item's fields via Jira APIs. In another automation, i also send a Slack message. The reason I put a re-fetch, is that the Slack message was being sent before those fields from the API have been updated. So that slack message with those fields would come out empty. When i added all those re-fetch, those fields were eventually populated and i sent the Slack message. The problem as you can see causes this LOOP status in other automations.

So i guess the problem is not the LOOP status but rather how can i prevent using re-fetch by delaying an automation? Does that make sense?


Here are the re-fetch...its crazy!

Screenshot (39).pngScreenshot (40).png

Alex Koxaras Community Leader Dec 07, 2021

Have you selected in the rule to which you send a web request, the option "Delay execution of subsequent rule actions until we've received a response for this webhook"?

Do you mean that checkbox in the rule details? If so, then Yes.

hey @Alex Koxaras now i removed most of the code from this and still happening. I assume it is cause its sending it before the other automations run. Regarding the checkbox in the rule, yes, it is checked. Going mad :-)

@Alex Koxaras ok i think i got it. I did a bit of a workaround. Instead of changing the priority no created issue, i waited for it to change a status, only then that automation runs and so is the next ones I needed. So I removed the re-fetch as it is no longer needed.


Suggest an answer

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

Next level incident management in Jira Service Management

Hello Atlassian Community! We’re thrilled to announce some exciting changes to incident management in Jira Service Management Cloud, in order to give your teams extra muscle during incidents, and ...

1,699 views 21 12
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