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; } } }

Automation all of a sudden not working

Nadege_l19417

We have an automation that runs daily from Monday to Friday everyday and it usually works with no issues. But today it did not run at all. No errors occurred either, it just didn't run so there is no event for today.

What could this be? I have attached the CRON expression in case it helps. Rule is enabled and had done no changes to it so not sure what I can do to resolve the issue. CRON Expression.png

UPDATE: The automation ran but much later than it should. As can be seen from the times below, it usually runs at around 7:50am (as intended). Today it ran at 10:56 for some reason.

UPDATE 2: It ran another 2 times today, though I am suspecting this could be because I had opened the modify automation page.

Accepted answers

Bill Sheboy

Hi @Nadege

When was the last time the rule was modified? Could the next-start have been modified?

Next, there was a performance issue reported yesterday, although that seems workflow related: https://jira-software.status.atlassian.com/

Regarding when scheduled rules trigger, my understanding from community posts by Atlassian staff is: if there is an Atlassian outage impacting rules, a scheduled rule could run later or even not at all. (i.e., there does not appear to be a "catch up scheduled rules" mechanism in the rule engine)

If none of these apply I recommend working with your Jira Site Admin to contact Atlassian Support to have them take a look. They may see something in the logging which is not visible to customers. https://support.atlassian.com/contact/#/ When you hear back from them, please post what you learn to benefit the community.