automation runs fine when triggered manually on one issue but won't run when scheduled

[Jo-Lee Bertrand]

I have two automations that are identical except or the fact that one is manually triggered and one is scheduled. I created the manually triggered one because the scheduled one would run in the sense that the audit log showed that it was scheduled, but nothing actually happened. When I run the automation manually from the work item, it works as expected. I was able to get the scheduled one to run once, but it failed every time after that. Could this be an automation limit thing? 

The automation is fairly straight forward. It looks for specific text in a field and if it finds it, it removes it.

[Richard · Accepted solution]

Could be an issue where when you run it manually, it only runs on the single issue where you triggered the rule. 

When scheduling it, you may need to look at what issues your automation is trying to find. You may be missing a step in your automation to find issues to action on.

[Richard]

Well, this may not be exactly correct, but like John said, screenshots would be helpful. And specifically, what the audit log of the automation failure states.

[Jo-Lee Bertrand]

Here is the automation. There is a query that definitely succeeds in finding the relevant issues (I checked) but the automation just never actually does anything. The exact same automation triggered manually works completely fine.

The audit log simply says NO ACTIONS PERFORMED and then if I click it, it says "scheduled".

[Richard]

It may be that check box in your screenshot that says "Only include issues that have changed since the last time this rule executed" 

If those issues haven't changed at all, even if they show up in your JQL, the automation won't run on them.

[Jo-Lee Bertrand]

oh my goodness! that was one of the default settings and I never thought to uncheck it. Thank you so much!!! I am in the process of testing it now. That would explain why it worked every once in a while but was not consistent.

[Jo-Lee Bertrand]

🤔that change made it run on one issue but then every subsequent running did not perform any actions. The query brings up at least 100 items that match the query.

[John Funk]

Hi Jo-Lee,

It's always good to show screenshots of any automation rules when posting a question. That being said, a couple of things - can you share a screenshot of the scheduled JQL?

Second, if you run the Scheduled rule immediately, what does it do? So go to the rule, then under the 3 dots menu next to Return to Rules, select Run rule. 

[Bill Sheboy]

Hi @Jo-Lee Bertrand 

Would you please post images of the following to provide more context:

• your current, complete rule in a single image
• images of the trigger, and of any actions, conditions, and branches
• an image showing the audit log details for the execution, remembering to expand all of the areas at the right side to show the details

Until we see those...

Have you tried the JQL for your scheduled trigger to confirm it returns the issues you expected?

When using the Field Values rule condition and testing for a value to "equals" something, it must exactly match the value to pass the condition.  Is this what you were expecting?

Kind regards,
Bill

[Jo-Lee Bertrand]

This is now working. Unchecking the box for only run on changed items largely fixed it. If the query returns a large number of results, it only seems to run on x number and then I just re-run it. Thanks Everyone!