Troubleshooting
Every error the app shows carries a code. Find the code here.
Diagnostics first
Confluence settings → Apps → Space Blueprints → Diagnostics shows the last inventory sweep, the rate-limit budget the app has used, queue health, recent failures and the app version. There is a "Copy diagnostics" button that produces a JSON block with no personal data in it. Attaching that to a support request usually removes a round trip.
SBC-100 — Validation
What happened. Something in the request could not be accepted: a missing field, a name that is too long, or a value that is not what the form expects.
What to do. The message names the field. Correct it and submit again. If the form itself looks wrong, reload the page: a stale tab can post an outdated shape after an app upgrade.
SBC-101 — The name does not match the naming policy
What happened. The blueprint has a naming policy attached and the proposed space name does not match its pattern.
What to do. The message shows the policy's own worked example. Follow that shape. Administrators can see and edit the pattern under Naming policies; if the policy is wrong rather than the name, fix the policy and the requester can resubmit without starting over.
SBC-102 — That space key or name is already taken
What happened. Between submitting and provisioning, a space with the same key or name appeared. The app re-checks immediately before creating, on purpose, so it never collides with something created in the meantime.
What to do. Reject the request with a note, and ask for a different name; or edit the key and retry. Keys cannot be reused from a deleted space until Confluence releases them.
SBC-103 — The blueprint no longer exists
What happened. The blueprint, or the space it was captured from, was deleted or archived after the request was submitted.
What to do. Re-capture the blueprint from a current space, then ask the requester to submit again. Existing spaces already provisioned from the old blueprint are unaffected; their inventory rows will show the blueprint as missing.
SBC-200 — Permission denied
What happened. Confluence refused an action the app tried to take.
What to do. Check that the app is still installed with all the permissions it was granted at install. An administrator can reinstall or upgrade the app to re-grant them. If the app was installed and the site's space-access model changed afterwards, run a sweep so the app re-reads the current mode.
SBC-201 — You need to be a Confluence administrator
What happened. A non-administrator tried to reach an administrative function. The app checks this on the server, not just by hiding buttons, so this can appear even from a bookmarked URL.
What to do. Ask a Confluence product administrator to perform the action, or to grant you that role.
SBC-202 — The app could not create a space
What happened. Confluence rejected the space creation itself.
What to do. Two usual causes. First, the site restricts who may create spaces; the app creates spaces under its own app identity, so the app must be allowed to. Second, the site is not using role-based space access and the legacy fallback is switched off in Settings. The message says which case it is.
SBC-300 — Rate limited
What happened. Confluence asked the app to slow down. This is not a fault: the app shares an hourly request budget across every site it is installed on, and it yields rather than pushing through.
What to do. Nothing. Provisioning resumes automatically, and the message says roughly when. Sweeps yield to provisioning, so an in-flight space request is never blocked by an inventory scan. If you see this constantly on a very large site, raise the sweep interval or lower the batch size in Settings.
SBC-400 — The page copy failed
What happened. Confluence's own page-hierarchy copy task reported a failure. The space itself was created; the pages did not all arrive.
What to do. Open the request and use Retry from this step. The app does not start over and does not create a second space. If it fails again, the copy is usually hitting a specific page: check the blueprint for pages with unusual macros or very large attachments. The app never deletes the partially filled space — an administrator can remove it manually if the request is abandoned.
SBC-401 — The page copy timed out
What happened. The copy task was still running after 60 minutes, so the app stopped waiting.
What to do. Check the new space: the copy may in fact have completed after the app gave up. If it did, mark the request complete from the request detail view. If it did not, the blueprint is probably too large or too deep; reduce it and re-capture. The 500-page cap exists to prevent this.
SBC-500 — Storage error
What happened. The app could not read or write its own data.
What to do. Retry once. If it persists, this is an app or platform fault rather than a configuration problem: send the diagnostics JSON to mira.maty@web.de.
SBC-600 — Licence required
What happened. The app's licence is not active, so actions that change something are refused. Reading still works, so an administrator can see the state of things.
What to do. Check the subscription in Manage apps. A lapsed licence also pauses the weekly inventory sweep. Nothing is deleted: your blueprints, requests, inventory and audit trail are all still there when the licence is restored.
SBC-900 — Unexpected error
What happened. Something the app did not anticipate.
What to do. Copy the diagnostics JSON and send it to mira.maty@web.de with a note about what you were doing. The diagnostics contain no page content, no names and no email addresses.
Situations without an error code
A request sits at "Provisioning" for a long time. Large page trees take longer; the progress bar reflects Confluence's own reported percentage. If it has not moved in 15 minutes, open Diagnostics and check whether the app is paused for rate limiting.
The inventory looks out of date. It refreshes weekly. Use Run sweep now, or Re-check now on one space. Space creation and deletion update immediately; role and label changes wait for the sweep.
A space shows as "drifted" and it should not. Drift means the space's roles, labels or owner no longer match its blueprint, or the review date has passed. If the change was intentional, re-capture the blueprint or update the review date from the inventory; the app reports drift, it never silently reverts anything.
Whiteboards and databases are missing from a provisioned space. They are never copied. Confluence's copy task does not carry them, which is stated on the blueprint before you confirm it and in Known Limitations.
The app says the site is using the legacy creation path. The site does not have role-based space access yet. Spaces are still created; the blueprint's access configuration is not copied, so set access manually afterwards. This resolves itself when the site completes Atlassian's roles rollout.