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

Why is the rule not executing consistently?

In Heo

The rule is designed to execute every minute to check if a ticket was created 1440 minutes (exactly 24 hours) ago, but not beyond 1441 minutes. However, there have been irregular time gaps in its execution, indicating it’s not functioning as intended. What could be the potential cause for this inconsistency?

Screenshot 2024-09-06 at 11.47.07 PM.png

Accepted answers

Aron Gombas _Midori_

@In Heo It is an implementation detail, but in the background "pending executions" will be put to a global queue (of work-to-be-done), and a pool of workers is working on them.

In this case, your scheduled execution will be put the queue, but it is impossible to tell how many other executions are also waiting in the queue. All in all, the latency of actually starting your scheduled execution is impossible to estimate. It will vary depending on the load.

Simply, you should not rely on the precise start time. There is no guarantee for that. You have to accept the random latency.

All comments

Michel Neeser

Hi @In Heo

Is your automation rule running for more than one minute? A scheduled rule can only run once at a time. So if the run time is more than one minute, the next executions of the same rule may be postponed or even skipped.

In Heo

Hi @Michel Neeser

thanks for your input. I’ve considered the scenario you mentioned, but it seems the execution time consistently takes less than 1 second.

Screenshot 2024-09-07 at 12.01.45 AM.png

Michel Neeser

@In Heo If I recall correctly, the minimum scheduling interval used to be 5 minutes. While I know that this is no longer the case, I can imagine that, from a technical standpoint, there might still be some limit in place to prevent excessive system load. It may be worth asking Atlassian Support regarding this.

In Heo

Alright, but isn't this something for Atlassian support...?

Aron Gombas _Midori_

@In Heo It is an implementation detail, but in the background "pending executions" will be put to a global queue (of work-to-be-done), and a pool of workers is working on them.

Simply, you should not rely on the precise start time. There is no guarantee for that. You have to accept the random latency.

In Heo

Totally understand the situation now. Appreciate the details!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud