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

"Query returns more than 100 issues" - error on automation, uanble to edit

Paul Madison

How do I make changes to this automation when this message keeps coming up?

Full Error:

Your query returns more than 100 issues. This can cause excessive load and as a result you can only schedule this rule to run at most 4 times in a 24 hour period. Please increase your interval, or reduce the number of issues your query returns.

Accepted answers

Paul Madison

Atlassian support helped me find my solution:

There was a CRON expresssion on the Scheduled trigger, which was why we got the error. We were just using the basic, but apparently having a CRON expression on there can cause this.

All comments

John Funk

Hi Paul,

You need to modify your JQL query to return less than 100 rows.

Trudy P Claspill

Or change the schedule of the trigger so that it will not run more than 4 times in a 24 hour period.

Paul Madison

So I seriously can't run a scheduled automation against more than 100 issues?

That's a poorly designed system and enough for me to consider switching to another product.

The automation only runs once a day, and even though it won't let me edit it, it runs without an error against 400+ issues.

This is either a false error or a bug.

Dan.Tombs

@Paul Madison

I won't lie I tend to ignore messages like that. automation rules have an in built throttling point anyway. I have ran automation rules that run against 1000's of issues at a time. The load isn't terribly noticeable in regards to overall system performance.

I always do suggest however, making sure your JQL statement actually does match the criteria you need. What are you trying to do with those issues found in the JQL statement?

Paul Madison

I would ignore this message if it would let me, the problem is I can't publish a small change to the automation.

I've got a ticket open with Atlassian, I suspect this is a bug.

The automation is only scheduled to run once a day, so as far as I can tell it is within the criteria the error indicates.

Paul Madison

Atlassian support helped me find my solution:

There was a CRON expresssion on the Scheduled trigger, which was why we got the error. We were just using the basic, but apparently having a CRON expression on there can cause this.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-service-desk

jira-service-management-cloud

jira-service-management