DOCUMENTATION
Troubleshooting
The messages the app can show you, what each one means, and what to do about it.
The template page
Everything starts from one existing page. Most problems here are the URL.
Invalid Confluence URL format. Expected: …/wiki/spaces/SPACEKEY/pages/PAGEID/…
The URL is not a Confluence page address — often a search result, a shortened link, or a URL copied from the editor rather than the page.
Open the page you want to clone, then copy the address straight from the browser bar. It should contain /wiki/spaces/ and /pages/.
Could not extract page ID from URL. Please use a direct Confluence page URL.
The address is Confluence but has no page ID in it — a space overview or a dashboard link rather than a page.
Navigate to the specific page first. A page URL carries a numeric ID; a space URL does not.
Page with ID … not found in space …. Make sure the URL is correct and you have access to this page.
The page ID is well-formed but does not resolve — the page was moved or deleted, or it is in a space you cannot read.
Open the URL in Confluence yourself. If it does not load there, the app cannot reach it either.
Please select a template page first
You moved on before a template was chosen.
Pick the source page in step one. Everything after it — naming, placement — is derived from that page.
Naming the copies
Every copy needs its own title. Confluence requires titles to be unique within a space.
Name all … pages before continuing. / Please fill in all … page titles
One or more of the new pages has an empty title.
Fill in every field. If you meant fewer copies, reduce the count rather than leaving titles blank.
A copy failed with a title conflict
A page with that exact title already exists in the destination space.
Titles have to be unique per space. Add a distinguishing suffix — a date, a team, a quarter — and run the failed ones again.
Where copies land
Copies can sit under an existing parent, under a new one, or at the space root.
Please select a Confluence space
No destination space was chosen.
Pick the space the copies should be created in. It does not have to be the space the template lives in.
Please select a page organization option / Please select a parent page
The placement step is incomplete — the app will not guess where 25 new pages should go.
Choose one: child pages under a parent you pick, child pages under a new parent the app creates, or pages at the space root.
Please enter a title for the new parent page / Failed to create parent page
You chose to create a new parent but gave it no title, or the parent could not be created — usually a title conflict or missing permission in that space.
Give the parent a title that does not already exist in the space, and check you can create pages there.
Running the clone
What to expect while a batch is being created.
Loading is taking longer than expected. Please try again or contact support if this persists.
Reading the space or the template page ran long — usually a very large space or a slow response from Confluence.
Try again. If it keeps happening on the same space, narrow the search rather than loading everything, and tell us which space so we can look at it.
A clone finished but some pages are missing
Pages are created individually, so a partial result means some succeeded and some did not — most often a title conflict.
Check the summary at the end: it lists what was created. Re-run only the ones that failed, with titles that do not already exist.
Macros or attachments did not come across
Cloning copies content, formatting, images, video, macros, labels and attachments. A macro that points at the original page can still render differently in its new location.
Macros that reference a specific page or space by ID keep pointing at the original. Update those on the copies, or use a macro scoped to the current page.
Results that are not quite complete
A run can create every page and still not manage everything it set out to do. Rather than report plain success, the results screen names what did not carry over and marks the pages affected.
N pages could not be placed in order; they were still created. Drag them in the page tree to reorder.
The pages exist and their content is correct — only their position failed. Confluence refused the reorder call, most often because the app is running an older version on this site that lacks the permission that call needs.
Reorder them by dragging in the Confluence page tree; nothing needs recreating. To stop it recurring, ask a site admin to update the app: Apps → Manage apps → Bulk Page Cloner, then update. Major updates are not installed automatically, so a site can sit several versions behind without anyone noticing.
N pages did not receive the template’s labels; the page content was still copied.
The same cause as ordering above. The pages and their content are intact; only the labels are missing.
Add the labels by hand, or update the app and clone again. Affected pages are marked no labels in the results list, so you do not have to guess which.
N pages were created without attachments; page content was still copied.
The app fell back to rebuilding the page from a stored copy instead of using Confluence’s native copy, which is the step that carries attachments across. Usually the template was captured in a way that left no source page to copy from.
Attach the files to the new pages yourself, or re-pick the template from the page list — rather than by pasting a URL — and clone again.
Licence
The licence is checked when you create pages. Browsing, picking a template and naming copies all work either way.
This site’s licence for Bulk Page Cloner is no longer active. Renew it in Manage apps to start creating pages again.
Atlassian reports this site’s subscription as expired or cancelled. It is not about your Confluence permissions — creating pages is unavailable for everyone on the site until it is renewed.
A site admin renews from Apps → Manage apps in Confluence. Your chosen template and typed titles stay on screen, so the same run goes through afterwards with nothing to redo.