About JSM Automation Limitations

[青山 明]

As a result of processing many issues with JSM automation, it seems that all of them have not been processed and ended in the middle. If you process many issues with automation, will there be interruptions in the middle?
Are there any restrictions?
Looking at the audit log, the processing time ended in about 600 seconds.

[Ismael Jimoh]

Hi @青山 明 

The short answer is yes. Especially if you are using the newer automation.

The automation is based on the rate limit here: https://support.atlassian.com/cloud-automation/docs/differences-between-automation-in-jira-server-and-jira-cloud/#

[青山 明]

Does the number of rules that can be processed per month mean the number of issues to be processed?

[John Funk]

No, it means the number of times the rule fires. 

[Ismael Jimoh]

If it takes too long to complete, if memory serves me well, this could be terminated if it is taking too long to be completed.

As such the recommendation is often reduce the filter to a manageable size and as @John Funk @asked, it’ll be great to know the trigger event

[青山 明]

I am using the cloud version. Is the cloud version the same?

[John Funk]

Hi @青山 明 

How many issues are you trying to process? What is the trigger used by the rule? 

[青山 明]

I'm trying to process about 400 issues.

About 400 issues are subject to JQL search.

[John Funk]

Can you share the rule? Is it a Global Rule? Or for just one project?

[青山 明]

Rules for one project.

JQL specifies updated > "-2w".
The number of hits is about 400.

[John Funk]

Then there should not be a limit for the number of executions. But you need to try not to process over 100 at a time. 

[青山 明]

What is the reason why you can't process more than 100 cases at once?

[John Funk]

Sorry, that should have been 1000