For AQL not working when trying to return a record due to 50 record limit

Question

Hi there,

I have a small automation rule that should be deriving where I have and empty 'Owner' attribute (which is a user) in Assets and then update it with the account ID.

This is a global rule.

I have a For AQL statement in place

objecttype = People and "Owner" is empty

within that statement I have a send web request which is a GET that looks like this

https://mysite.atlassian.net/rest/api/2/user/search?query={{object."EmailAddress"}}

EmailAddress is the value that is stored against a user in Assets

I am only getting 50 records back which is pretty pointless really when there are a couple of hundred records it will need to go through.

Is there a way around the 50 record limit or is this a failed exercise from the get go?

Thanks

Ste404 · Answer

Yeh I will break it down into smaller scheduled tasks and see how it runs over the course of an evening, should be able to achieve what I want that way.

cheers

Bill Sheboy · Answer

Nope.

I believe the limit is 100 items and then paging must be used with repeated calls.  And when processing many items it is possible the rule would run into one of the service processing limits for automation rules, and so halt.

When you are trying to make a bulk change like this with an automation rules, one approach is to clearly identify what needs to be processed (to identify a stopping condition), schedule a rule every few minutes/hours to process a chunk, and let it run until done.

Ste404 · Answer

hmmm so I could have maxResults as 500 for example...  then another automation as a scheduled task to pull in another 500.   If these were going to run through the night and there was 2000 records as a round number, I could just in theory have 4 automation rules if I wanted to cover off 2000 records with no Owner.

Not sure how that all hangs together in my GET statement but not sure if I am on the correct track