Provisioning normally fires automatically when the setup form is submitted. The panel keeps the per-step results from the last run — so a partial failure is diagnosable after a reload, not only in the moment — and offers a retry that reuses the existing account and re-runs the missing pieces.
Also called: my account never got set up · setup failed · provisioning error · half-created account
- 1Each step returns ok plus a note; the whole map is persisted on the signup.
- 2The Signups page and the account's Contract tab both render the last run, tick or cross per step.
- 3Retry posts the signup id; the library reuses the existing account rather than creating a second one.
- 4A partial result comes back with the failing step named instead of a single red banner.
The route describes itself as the repair path: 'Provisioning normally fires AUTOMATICALLY on intake submit — this endpoint is the operator's RETRY/repair path (the lib is fully idempotent: it reuses the existing org and only re-runs the steps that failed).' The persisted step map exists because 'a partial failure is diagnosable after a reload, not just in the transient post-click result panel.'
- A partly-failed setup looked identical to a total failure.
- Retrying risked creating a duplicate account.
- The failure detail vanished on reload.
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →