nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

why is the status of the automation says 'no actions performed' while it actually worked?

Yousuf Al Rawahi

I have created an automation when an issue is created, it will automatically create 6 subtasks, this works perfectly. But then I have created another automation, when the issue is created, and if certain conditions are met (as shown below), it will attach a form to a specific subtask. When I checked, it actually worked, but when I checked the audit log, it says 'no actions performed'. And it's checking on a wrong subtask (which is 'SCRM-134'), while it should check on 'SCRUM-129'. What could be the problem here?

Screenshot 2024-04-03 120546.png

Screenshot 2024-04-03 120529.png

Screenshot 2024-04-03 120509.png

Accepted answers

Bill Sheboy

Hi @Yousuf Al Rawahi

From what you describe, you have two automation rules, and the actions of one (create the subtask) will trigger the other (to attach the form). This second rule has probably enabled the option "Allow Rule Trigger".

The Issue Created trigger can fire so quickly that some issue data may not yet be available to the rule. This will appear as symptoms like rule errors, missed conditions, or other unexpected behaviors. As you are using two rules chained in sequence, I hypothesize this effect is more likely to occur.

The fix / work-around is to always add the Re-fetch Issue action immediately after the Issue Created trigger. This will slow the rule down a bit, reloading the data before the rule steps proceed. Please try adding that action to your second rule and re-test.