Problem

When configuring Confluence automation using the For each inactive page branch (docs), the behavior is influenced by internal rules that are not visible or configurable to admins.

Currently:

• Parent pages are not treated as inactive if they have any child pages that is still considered active. The parent only becomes eligible after all children are inactive.
• Archived pages are excluded from the inactive-page logic and are never considered by the branch.

Because these rules are not surfaced in the UI or documentation for the branch configuration, admins can see fewer pages being processed than expected without understanding why.

This makes it difficult to design, troubleshoot, and trust automations that rely on inactive content with confidence.

Suggested Solution

Add explicit, configurable options to the For each inactive page branch that control how parent and archived pages are handled, for example:

• A checkbox or dropdown such as:
• Include parent pages even if some child pages are active
• Treat archived pages as eligible inactive pages (or explicitly exclude them)
• UI messaging or a help tooltip in the branch configuration that clearly explains:
  • How parent/child relationships affect inactive status
  • How archived pages are treated
• Update public documentation for the branch to describe these options and the underlying logic.

This would align the inactive-page branch with other Confluence actions (such as moving or copying a page), where users are clearly alerted about including or excluding child pages and can make an explicit choice.

Why This Is Important

• Admins designing clean-up or review workflows for stale content need to know precisely which pages will be targeted. 
• When some pages are silently skipped, it appears that the automation is unreliable or broken. 
• Confluence already warns users and lets them choose whether operations should apply to child pages (for example, when moving or copying pages). Providing similar control in automation ensures a consistent and intuitive experience.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available.