Automation Service Limit Web Requests

[Sofia Reid]

Hi, 

I have an automation that sends a GET request to tempo and retrieves all the worklogs for a singular project in a day. 

It then branches and for each worklog collected it sends another web request ( PUT) editing one of the worklog fields. 

What are the limitations of this approach ? Project will be used by approximately 30 people. I am expecting it to process around 500-750 worklogs a week with the majority being on a friday.

I am thinking of running the automation either every day or once a week depending on the Jira automation Service limitations.

[Bill Sheboy · Accepted solution]

Hi @Sofia Reid -- Welcome to the Atlassian Community!

What is your Jira Cloud license level and which Atlassian products are you using?  Please confirm these with your Jira admin, and then check your automation's global usage data to see the impact of your rule(s).

The answers are important because in October 2023 the packaging model for automation rules changed, and so the limits on what counts and the allowed counts permitted per month changed.  Please look here to learn more about those changes:

https://www.atlassian.com/blog/announcements/cloud-automation-packaging-update

Also, from what you describe, your rule could potentially run into other service limits: processing time, number of items per looping, etc.  Please read about the other service limits here:

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

Kind regards,
Bill

[Sofia Reid]

Hi Bill, Thank you for your help.

I have found that I can process at least 200 worklogs in an automation branch ( I haven't tested more as I overestimated the amount of worklogs).

I believe the site I will be using the automation on is premium so there shouldn't be an issue with the amount of runs possible.