Automation flow not triggering

[Stephen Finegan]

I have an automation set up to go off every day at 9am (if my math via UTC in the cron is right, I'm CST), and when I check it, it even says that 17 tickets currently will be affected by it, but it's simply not going off. These 17 tickets did not just reach this status as of today. This rule has been created long enough that these 17 should be affected by it as of last Wednesday. Can someone please help me understand where I am wrong here so that it can trigger properly? I am not receiving any errors about it not going off, it's just simply not going off.

[Christopher Yen · Accepted solution]

Hi @Stephen Finegan 

the 17 items shows that the JQL is matching those work items, I would try unchecking "only include work items that have changed since the last time this flow executed" 

I'm not sure if the cron is correct but it seems like you could achieve that same schedule using the out of the box schedule UI, I would try the normal 1 week occurrence with the days of the week checked + time zone and see if it triggers. 

With scheduled flows you can always manually trigger it as well to test if there is any errors with the action eventually but it does seem like your issue is with the trigger/schedule first.

[Stephen Finegan]

Wow, I am dumb. Somehow I completely missed that selecting the "week" option allowed me to select days it runs on. Thank you for pointing this out, that's significantly easier than messing with cron.

Another person suggested unchecking that box as well, so I've done so and will be testing with that, and should know by tomorrow morning if it's functioning properly now.

[Stephen Finegan]

@Alan Bruce @Christopher Yen As of this morning, it appears to be functioning correctly. Unchecking that box seems to be the solution I needed. Thank you both for your assistance, and I hope you have no errors for the remainder of your days.

[Alan Bruce]

You could maybe try this:

status = "Waiting for Customer" AND updated < startOfDay(-3)

[Stephen Finegan]

I'm having a hard time understanding why this would affect it. I can give it a try, but isn't the timeframe what the cron expression is for in the first place?

[Alan Bruce]

I usually create a test ticket and test automation and then run a test from there to check first. 

You can also 'Manually' run any Scheduled Automation to see if it works as well.

[Stephen Finegan]

My testing showed it working previously, and manually running it functions properly, so that's why I'm really confused about this. I've tried the other thing you suggested, and I'll be running more tests to determine if it's going to function properly. I should know by tomorrow morning, as I have a similar rule that I've made the same changes to which should go off tomorrow.

[Alan Bruce]

Your automation logic is a bit confusing to.

• Run Monday thru Friday
• Look for tickets not updated in last 3 days.

So if a ticket was not updated on Friday, Saturday, Sunday - Close it on Monday?

There is a way you can add some business day logic in if needed but if it works for you then thats fine too.

Was this working already and then it stopped working or is this the initial set up?

[Stephen Finegan]

I would actually love if you could give me tips on how to add business day logic to this. I wasn't entirely sure how to do this originally, so if there's any information you can provide regarding it, I'm all ears.

[SONASHREE S]

Hi Stephen,
Can you please add the screenshot of the Audit log, so that it better helps understand the situation here. 
Additionally,
1. Who is the actor for this automation and does that user has permissions like 
- Browse project
- Add comments
- Transition issues
2. In the automation I can see that you are trying to transition to Done. Does your workflow support this? 
I mean to say does your workflow has a transition from status "Waiting for Customer" to "Done"

[Stephen Finegan]

The audit log won't help because there are no instances of this anywhere inside of it. It isn't failing, it's simply not running at all.

The actor is Jira Automation. This is what we use for everything in our automation rules. It has permissions to browse projects, add comments, and make transitions, and I use it for doing all those things in other rules successfully. In fact, if I try to run this rule manually, it actually does succeed with zero problems. My issue is that it isn't automatically running, not that it's failing when trying to run.

[Alan Bruce]

Oh, maybe you need to check/uncheck the box at the bottom of the trigger: Only include work items that have changed since the last time this rule executed

[Stephen Finegan]

It's currently checked, so I will uncheck it and see if this helps. Thanks for the idea!