Page Lifecycle

AutoPage - Page Lifecycle

This page explains what happens when an AutoPage rule is triggered — from initial page creation through subsequent updates and edge case handling.

---

Page Creation

When a rule fires for an issue that does not yet have a linked Confluence page (for that rule), AutoPage performs the following steps:

1. The issue is loaded and validated against the rule’s conditions.
2. A new Confluence page is created by copying the configured template page.
3. The page title is set using the configured title template (with placeholder substitution).
4. Labels and copy options (attachments, permissions, labels, custom contents) are applied as configured.
5. A link between the Jira issue and the new Confluence page is established.
6. An audit log entry with status PAGE CREATED is recorded.

---

Page Update

When a rule fires for an issue that already has a linked Confluence page (from the same rule), AutoPage updates the existing page instead of creating a new one:

1. The existing link is found by the rule ID.
2. The linked Confluence page is retrieved.
3. The page title is updated (if the title template uses placeholders that have changed).
4. Page labels are updated to match the current rule configuration.
5. An audit log entry with status PAGE UPDATED is recorded.

Note

The page content is not replaced on update. AutoPage macros using “Live Update” sync mode will automatically show current Jira data. Macros using “On Page Update” sync mode will have their content refreshed during the update.

---

Orphaned Pages

A Confluence page can become “orphaned” if its parent page is deleted or if the page tree structure changes. AutoPage detects orphaned pages (pages without a parent) and automatically reparents them to the configured destination parent page during the next update cycle.

---

Concurrent Execution Control

When multiple events fire simultaneously for the same Jira issue (e.g., an issue is updated by multiple users at the same time), AutoPage uses a locking mechanism to prevent concurrent execution:

• A lock is acquired per issue before rule execution begins.
• If a lock is already held, AutoPage waits up to 30 seconds for the lock to be released.
• If the timeout is reached, the lock is forcefully released and execution proceeds.

Tip

If you experience issues with stuck locks (e.g., after an unexpected error), an administrator can manually reset the lock via the Admin Settings. See the Getting Started guide for details.

---

Retry Behavior

If a rule execution fails due to a transient error (network issues, service unavailability, timeouts), the Forge platform automatically retries the execution:

• Maximum retries: 4 attempts
• Retry delay: 10 seconds between attempts
• After all retry attempts are exhausted, the error is logged in the audit log and the execution is abandoned.

For more details on monitoring rule executions and errors, see the Audit Log documentation.