Issue Summary

Jira has rate limiting on issue edits that also applies to creating children.

Steps to Reproduce

Create a rule that clones an epic and then all children (at least 100 children).
It can also occur if there are lots of other rules that are triggered on the created parent issue (that subsequently edit the issue)

Expected Results

All issues are created successfully

Actual Results

The rule gets half way through creating the children and it 429s

Workaround

Pre requisites: check the audit logs from the automation rules to confirm that the cause is 429.

Steps : there are a few suggestions to improve the performance of rules, to help avoid this problem.

• Review and reduce the load on Jira by examining other rules triggered when a parent issue is created. This can help prevent cascading edits that contribute to exceeding the rate limits.
• Adjusting the schedule of the automation rule to a time with less activity. Rate limiting can result from multiple concurrent actions, not just a single rule.

Reference documentation:

• Best practices for optimizing automation rules
• Automation Service Limits