Rule triggered by cron expression triggers twice, one hour apart.

[Jakob KN]

Hi folks! 

I've got a number of recurring tasks that's being created by Automation for Jira. 

They're all using the scheduled trigger with a cron expression, and are creating various tasks for our recurring internal instance maintenance (such as revising inactive accounts, SSL cert. expiry, assessing upgrade options, etc.)

The issue I'm having is that the rules all trigger twice, one hour apart. 
To give an example, I've got a rule with cron expression: 0 0 10 ? 1/6 MON#1 *

This should trigger once on the 1/1-2024 at 10:00, however it triggered both at 09:00 and 10:00. 

I'm on the latest version of the Automation for Jira app (9.0.3). 
System time is the same as the time zone set on my account (gmt+1)

Any ideas as to why this is happening?

[Bill Sheboy]

Hi @Jakob KN 

First thing, I am using Jira Cloud (not Server or Data Center) and so I am making suggestions based on what I know about rules and not Jira Server / Data Center specifically.

That expression looks valid, according to the documentation: https://confluence.atlassian.com/jirasoftwareserver/constructing-cron-expressions-for-a-filter-subscription-939938814.html

I recall reading about a problem that if a scheduled trigger had ever been saved with a basic schedule (i.e., fixed rate of every...) and then changed to a CRON expression that both could persist.  Have you tried recreating the rule, adding only the CRON expression before saving it?

Kind regards,
Bill