Automation works in one space but not another? Attempting to change page statuses
Asked by Heather Blue:

Any idea why an automation rule would run successfully in my personal space but not in a separate shared space?

I'm the admin of our knowledge base and I'm trying to assign the status "up to date" to all pages that don't already have a page status. It worked flawlessly in my own space, but no page statuses changed in the knowledge base space, even though it says the rule ran successfully, I couldn't find any pages that had the status changed.

Perhaps a permissions issue or usage one? Our knowledge base has 3k pages vs a few in my own, potentially it can't run through that many pages at once? There's also some pages in our knowledge base that I can't edit (technically I could add myself as an editor to those pages since I'm an admin), but if either of these were the issues I'd imagine it'd say there were "some errors" or the rule failed, yet it says it was successful.

I can't figure out why it won't run, the rules are identical. Any advice appreciated!

![Screen Shot 2023-12-13 at 2.55.38 PM.png](https://community.atlassian.com/t5/image/serverpage/image-id/296714iFE382DCBEF0F111F/image-size/large?v=v2&px=999 "Screen Shot 2023-12-13 at 2.55.38 PM.png")


Answers:
author: Ste Wright
body: Hi [@Heather Blue](/t5/user/viewprofilepage/user-id/5138759)

What does the audit log say for this rule when it tries to run?

Is it possibly hitting a service limit? Do you still have enough executions?

Check service/execution limits here...

* <https://support.atlassian.com/cloud-automation/docs/how-is-my-usage-calculated/>
* <https://support.atlassian.com/cloud-automation/docs/automation-service-limits/>

---

Possibly it's the "Number of items a branch can retrieve per rule run" - which is...

* "For each page" branch: 150 pages

\^ Could you limit the branch to locate 150 pages and see what happens?

Ste

comments: author: Heather Blue
body: [@Ste Wright](/t5/user/viewprofilepage/user-id/1166470) ah you've probably identified the issue, I didn't realize it had execution limits, so that'd explain why it couldn't change all 3k pages in our knowledge base. It appears it did change *some* statuses, but random pages, and far from all of them.

When it ran, it said "success" -\> the associated items said "none" but there were some pages I found that did change. In my personal space the associated items also said "none" but all pages changed. The following times it ran in the knowledge base it said "no actions performed".

If it only processed 150 pages the first time, I wish it would've continued running through the rest of the pages the following times, but it appears it went through the same 150 pages each time the rule ran, thus explaining the audit log actions.

I've tried updating the rule so it looks at \<150 pages at a time, but I'm struggling to revise the rule to do so. We title all pages with department abbreviations, so I thought that could be a good way to look at them in batches, but I wasn't able to get it to work. I tried creating the rule so it'd look at pages by certain authors too and by creation dates, but automation isn't my strong suit so I think I'm missing something!

Would you happen to have any suggestions on how I could alter the rule so it'd limit the # of pages to \<150? Thanks for the response and helping me identify the likely culprit!

![Screen Shot 2023-12-14 at 11.30.50 AM.png](https://community.atlassian.com/t5/image/serverpage/image-id/296888iF89303F14BBD74F9/image-size/large?v=v2&px=999 "Screen Shot 2023-12-14 at 11.30.50 AM.png")