Hi,
I’ve been trying to do this in Automation (Studio flows), but I keep running into problems and would love advice from anyone who’s solved something similar.
What I’m trying to do
I have about 75 technical standards pages in Confluence. I want each page to carry a lifecycle status as a label, plus an optional “overdue for review” flag. That means at most 2 labels per page:
standard-draftstandard-submitted (with the review board)standard-active, optionally plus standard-overduestandard-unknown, optionally plus standard-overdue
When a page’s status changes, the old status label should be removed and the new one added.
What I’ve built
A scheduled flow that branches over pages under a folder. A Rovo agent reads each page (and the attached PDF if needed) and returns a status word. Web requests then DELETE old labels and POST the new one via the REST API.
Where it breaks
- Remove label action. The built-in “Remove label in Confluence” action shows an empty label picker, so I can’t use it.
- Rate limits. Deleting every possible stale label per page hits HTTP 429s. The branch seems to run all pages in parallel, and Delay steps don’t help.
- Agent output.
{{agentResponse}} sometimes comes back doubled across pages, e.g. unknownunknown, which creates junk labels. - Smart value functions.
toLowerCase() and replace() on {{agentResponse}} return empty, so I can’t clean the value up before using it.
Questions
- Is there a recommended pattern for keeping exactly one label from a fixed group on a page (swap one status label for another)?
- Can a Studio branch run one page at a time, or be throttled?
- Has anyone used page properties, a status macro or a database in place of labels for this? Did that work better?
- Any other approach you’d recommend for document lifecycle on standards pages?