Help setting up automation to remove a label from a Confluence page when another label is present.

[Jolie]

I'm attempting to establish an audit process for our Confluence space to ensure our content remains current. The objective is to create a list within Confluence that identifies content that hasn't been updated in the last 6 months. However, I also want to exclude certain articles from this list, specifically those that don't require review or modification. 

Part 1.

Automation 1: Add automation to automatically add label "ts-review" to content that hasn't been updated within the last 6 months.
*This is working as intended.

Automation 2: Add automation for content we don't want to be flagged for review, remove tag "ts-review" on any article with the tag "ts-review-skip."
*This part returns the following error in the audit log: No CQL-compatible content found in the rule context; there is nothing to check against the CQL query. The CQL condition component can only follow components that involve CQL-compatible content, such as the blogpost published trigger, the publish new page action, or the related entities branch.

Part 2: Use "Content By Label" macro to pull all content with the label "review" in our Confluence Space.

Open questions

1. Why am I receiving an error in my audit log for the second automation?
2. If there isn't a way to remove a label with automation, would there be a way to set up alternative automation to achieve the same behavior? Not ideal, but for example, could we set up an automation to automatically re-publish content with a skip label so it gets excluded from the audit?
3. This could also be achieved without automation by using the "Content By Label" macro if there was the ability to exclude labels. Currently, there is only the ability to include. Is this something that is being looked into as a feature improvement?

[Avinoam · Accepted solution]

Hi @Jolie !

My name is Avinoam and I'm a product manager on Confluence Automation.

Referring to this support document and what you're describing, looks like what you need is the CQL branch which will use that cql to find and loop over all pages and perform those actions.

So, if you use the "related entities" branch for both rules, and consolidate all your conditions into the CQL for that branch component it should work.

Please let me know if this helped!

Thanks

Avinoam

[Jolie]

Thanks, Avinoan! Appreciate the help.