Troubleshooting Publish Content
The Publish content action copies a page to another location, usually another space. This page explains the most common reasons a publish fails or behaves unexpectedly, and how to fix each one.
If a publish action fails, you can view the actions history by opening the byline, clicking the ⋯ menu on the top right, and then clicking the ‘View actions’ menu item. This will show all actions for the workflow on the page, along with error details for failed actions. If you're an administrator, you can view the full action history across all pages for a workflow by navigating to the workflow in the workflows list (either at the space or global level depending on where the workflow was created), clicking on the ⋯ menu for the workflow entry row, and clicking ‘View actions’. The error noted in the actions history will usually name the cause of the issue.
Who needs permission to publish?
Publish content runs as one of two identities. Which one is controlled by the Publish page with transitioner as owner checkbox on the Publish content action.
|
Checkbox |
Who performs the publish |
Who needs the permissions below |
|---|---|---|
|
Unchecked (default) |
The Workflows for Confluence app |
The Workflows for Confluence app user |
|
Checked |
The user who triggered the transition |
The transitioning user |
The permissions required are:
-
Add pages in the destination space(s).
-
View the page being published, in the source space.
-
Edit permission on the existing published page(s), when you are republishing over pages that already exist.
-
Add restrictions in the destination space, if Permissions is selected under Add page data to published page.
Tip: If you want users to publish content without giving them any access to the destination space, leave Publish page with transitioner as owner unchecked and make sure the Workflows for Confluence app user has the permissions above. This is the usual setup for a read-only, customer-facing space.
If permissions are missing you will see an Insufficient permissions error.
Common mistakes
-
Checking "Publish page with transitioner as owner" without all potential transitioners having access to the destination space. With this option on, every user who can trigger the transition needs the permissions above. Either uncheck it, or limit the publishing transition to a small group of users who have those permissions.
-
Granting the app user permissions in only one space. The app user needs access to both the source and destination spaces.
-
Copying permissions into a space where the publisher cannot set restrictions. Either grant the publisher that permission or deselect Permissions under Add page data to published page.
"Error M0TDR9 … likely due to a page title conflict"
This error appears when republishing over an existing page in the destination (i.e., re-running the publish content action for a page which has already been published via the action) and Confluence returns an internal server error (HTTP 500). A title conflict is the most likely cause, but it is not the only one.
Check, in this order:
-
Duplicate titles. Confluence requires page titles to be unique within a space. If the title you have set for the published page (or the source page title, if you left the title blank) is already used by another page in the destination space, the copy will fail. Change the Page title on the Publish content action, for example by adding a variable.
-
Try copying the page with Confluence itself (⋯ > Copy, using the same parent). If this also fails, the problem is with the page data in Confluence rather than with Workflows. This can happen even when no restrictions are visible on the page, and can show as errors such as
NON_EXISTENT_USER_ID_VIOLATION. Contact Atlassian Support, and let us know the support request number so we can help.
Note: Renaming or deleting the existing destination page does not always clear this error, because the cause may be the source page rather than the target.
"Folders are not enabled"
If Clone page's parent hierarchy is selected and the page sits under one or more folders in the source space, Workflows recreates those folders in the destination space. Confluence rejects this if folders are not enabled in the destination space.
To fix it, either:
-
Enable folders in the destination space. This can be done from Space settings → General → Features.
-
Uncheck Clone page's parent hierarchy on the Publish content action and publish the workflow.
"504: Gateway Timeout"
Large pages can take longer to copy than Confluence allows. Workflows does not retry after a 504, because the page is often created anyway and a retry could create a duplicate.
Check the destination space before publishing again. If the page is there and up to date, no action is needed.
"HTTP 404" or "Error getting page title" in the byline or Document Control Table
A published page can display details about the page it was copied from, such as in the Workflows Document Control Table macro. The page ID and workflow information come from Workflows, but the page title is fetched from Confluence as the person viewing the page. If that person cannot view the original page, for example because it is in an editorial space they do not have access to, they see Error getting page title: HTTP 404.
This is expected behaviour. To avoid it:
-
Give those readers view access to the source page or space; or
-
Remove the macro from pages in the destination space, or clear Copy Workflows metadata from original page on the Publish content action.
Status is missing or not loading on published pages
If you remove a status from a workflow, any page currently in that status is left at a step that no longer exists in the workflow. Those pages show an unreachable step in the byline, and macros that show the workflow status can fail to load.
This also affects published copies where Copy Workflows metadata from original page is selected, because the published page displays the original's state as it was at the time of publishing.
To avoid this:
-
Before deleting a status, transition all pages out of that status.
-
When you delete a workflow or step, use the migration options described in Deleting and Migrating a Workflow | Deleted step.
Quick reference
|
What you see |
Likely cause |
Fix |
|---|---|---|
|
Insufficient permissions |
The app user or transitioning user lacks add/edit permission |
See Who needs permission to publish? |
|
Error M0TDR9 / page title conflict |
Duplicate title, or a Confluence-side error with the page |
See above |
|
|
A restriction referring to an account Confluence no longer recognises |
Remove the restriction, or try without copying permissions |
|
Folders not enabled |
Parent hierarchy cloned into a space without folders |
Enable folders, or clear Clone page's parent hierarchy |
|
504 Gateway Timeout |
Large page |
Check the destination space before retrying |
|
HTTP 404 in macro |
Reader cannot view the source page |
Grant view access, or remove the macro |
|
Unreachable step / status not loading |
A status was removed from the workflow |
Migrate pages to a new status before removing a status in a workflow |