Jira Automation How do I get around "Too Many Requests?"

Question

I created an automation to clone an issue and its 120 subtasks. Unfortunately my automation gets to exactly 50 subtask clones before failing with the nebulous and unhelpful error: "Too many requests." Searching the internet returns similarly nebulous responses from Atlassian.

So, I am asking: is there a way to add a rate limiter or something in my automation to stop this from happening?

Luka Hummel - codefortynine · Answer

Hi @TJ and welcome to the community!

If you are willing to use a third-party app, you might want to consider using our Deep Clone for Jira. Deep Clone can help manage extensive cloning tasks in Jira more efficiently. It allows for bulk cloning and provides advanced options for cloning issues and their subtasks. This could potentially circumvent the limitations you're encountering with the standard Jira Automation. Additionally, Deep Clone is designed to handle large volumes of data without triggering such errors.

Bill Sheboy · Answer

Hi @Trudy P Claspill and @TJ

I think that 50 limit is for subtasks in a single, create subtasks action.

The other limits could be from the branching of 100, which is still below the 120 noted by @TJ and / or the processing time limit for rule execution.

@TJ -- Please ask your Jira site admin to look at the global administration > automation rules > Performance Insights (at the top-right ... menu) to see if it indicates more detail on the rule.

Kind regards,
Bill

Trudy P Claspill · Answer

Hello @TJ

Welcome to the Atlassian community!

Reviewing this KB:

https://support.atlassian.com/cloud-automation/docs/automation-service-limits/

...indicates that a given rule can create no more than 50 sub-tasks.

You would need to somehow separate the cloning of the subtasks so that no more than 50 of them are created in a given rule execution.

120 seems like quite a lot of subtasks for a single parent task. Is there any way you can reorganize the work to split the subtasks between at multiple issues?

There might be a way to manage this by creating, say, a custom field to "group" the subtasks into groups of 50 or less, and then have multiple rules (or multiple executions of one rule) to get all the subtasks cloned. I have not tried to work out the details on how to make that work.