Help with CRON expression for Filter Subscription - every 30 minutes, every weekday, from 7am to 6pm

[Nathan Given]

My goal is to have the subscription run every weekday, every 30 minutes, from 7am to 6pm.

Thus, I tried to set it up using this cron expression:

0 0/30 7-18 ? * MON-FRI *

It ran yesterday just fine, but then stopped.  This is what I see on the subscriptions page:

It seems weird that the "next send" is set for yesterday?

If I open this and re-save it, then it will work for a day, but then stop working again.

I'm not sure why this only works for a day, then stops.

Thanks,

Nathan

[Mark Segall]

Hi @Nathan Given 

Your cron should work, but maybe you could try this to see if it's having an issue with the MON-FRI clause:

0 0/30 7-18 ? * MON,TUE,WED,THU,FRI *

[Nathan Given]

Thank you, right now I changed it to this for the next week:

0 15,45 7-18 ? * * *

 I know that that will cause it to run on the weekend, however, right now I need it to be reliable more than I need it to not run on the weekend.

Once I can confirm that the above works for a few weeks, I'll try your suggestion.

And thank you for confirming that my expression should work. I thought I must have been going crazy ( I even confirmed it here: https://www.freeformatter.com/cron-expression-generator-quartz.html )

[Bill Sheboy]

Hi @Nathan Given 

I checked the public backlog and did not see this symptom for scheduled triggers with CRON expressions in rules, but did see others (like firing when there was no data to process). 

You may want work with your site admin to submit a support ticket for this so Atlassian is aware of the problem: https://support.atlassian.com/contact/#/  When you hear back from them, please post what you learn to benefit the community.  Thanks!

Kind regards,
Bill