nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automated rule for identifying inactive pages isn't excluding labeled pages

erica.bogosian

Right now I'm testing an automated rule that is meant to flag inactive pages, but exclude any pages with a certain label. However, when I run the rule in my personal space, it keeps saying the test page I have labeled passed the condition.

Rule:

- Branch rule / For each inactive page

- Smart condition: If {{page.label}} does not contain auto-exempt

- Then: Log page

Result:

- Page with the label "auto-exempt" is logged

This seems like a very straightforward rule so I'm not sure what's going wrong here. The audit log isn't showing any errors.

Ideally I would like this rule to be able to exclude multiple labels from archival as well.

Accepted answers

Tomislav Tobijas

Hey @erica_bogosian ,

Try using the following Labels smart value instead (in the condition):

{{page.labels.name}}

I believe this should cover it.

What you could also do, while troubleshooting automation rules, is to use Log action to see outputs of things like smart values 👀

Cheers,
Tobi

All comments

Chris Rogers

Hi @erica_bogosian

Are you able to post a screenshot of your existing rule? With automation, I definitely find it helps to see how you've set up the flow of the rule so I can try and re-create it and test.

Tomislav Tobijas

Hey @erica_bogosian ,

Try using the following Labels smart value instead (in the condition):

{{page.labels.name}}

I believe this should cover it.

What you could also do, while troubleshooting automation rules, is to use Log action to see outputs of things like smart values 👀

Cheers,
Tobi

erica.bogosian

Great news! that seemed to work. At least, the labeled pages are now being excluded from the log. It doesn't seem to be able to log the label name, though - but that's small potatoes.

Screenshot 2025-12-16 090217.png Screenshot 2025-12-16 090357.png

erica.bogosian

Okay, so thanks to @Tomislav Tobijas , I have a solution. However, that's lead into a new problem:

I'm realizing that, because of how the rule is set up with branching, those label exemptions only apply to the first branch. Duplicating the condition on the second branch doesn't seem to exclude the labeled page ("wweh") from the email report.

Screenshot 2025-12-16 091036.png Screenshot 2025-12-16 091105.png

Is there a way I can set up the automation so that the second branch excludes the labeled pages as well, or only pulls the pages logged/archived in the first branch?

Tomislav Tobijas

@erica_bogosian ah, so you want to get like 'grouped' results for each owner instead of separate emails being sent for each page?

If so, there are a lot of limitations that will probably make this impossible (but, never say never). I've tried using Lookup actions and also smart values such as {{inactivePagesPerOwner}}, but with no success

Lookup action does say this:

For example, you could set your rule to run only on pages created by a certain person more than six months ago. Let’s say that Sarah has 200 pages from more than six months ago. Building a rule without a lookup action would result in Sarah receiving one email per page. By adding Lookup pages to your rule, she will receive just one email referring to all pages.

But the output of {{lookupPagesPerOwner}} is not what you would expect it to be so I couldn't find a solution there 🫤

Any chance you've tried Rovo agents within automation rules to check how it will handle this requirement?

erica.bogosian

ah, so you want to get like 'grouped' results for each owner instead of separate emails being sent for each page?

Exactly, rather than someone getting fifteen individual emails for each of their archived pages...

I guess I can keep testing/experimenting with that Lookup pages variable. Tbh, I haven't touched Rovo yet, I generally avoid AI where I can help it.

Tomislav Tobijas

You could check with Atlassian Support and see if they can provide some insights about this smart value: {{lookupPagesPerOwner}}

In theory, this should resolve your problem, but from a couple of tests I performed, this is returning a format in which there's no information about the actual owner (e.g., their email address), in order to send out emails to those users 👀
It might be a bug, or maybe the documentation for it is incorrect.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud