# Provisioning issues

If your instance seems stuck or fails during setup, here's what each stage
in [Create your first ERP instance](../getting_started/first-instance.md)
is actually doing, and what a stall at each one usually means.

| Stage | What's happening | If it stalls here |
|---|---|---|
| Creating PostgreSQL Database | Creates your dedicated database | Rarely stalls — a hang here usually means a platform-side database connectivity issue |
| Creating Odoo Container | Provisions your isolated environment (namespace/PVCs on Kubernetes, or the container + volumes on Docker) | Can take longer than expected if storage provisioning is slow |
| Initializing Odoo | Installs Odoo's base module into your new database | The most failure-prone step — see below |
| Finalizing Tenant | Final configuration + DNS | Can briefly stall while your domain propagates |
| ERP Instance Ready | Done | — |

## If it fails during "Initializing Odoo"

This step runs Odoo's own database initialization inside your instance. It
can fail if the instance was sized too small for the initial install — if
this happens repeatedly, try a plan with more memory, or contact support
with your instance name so it can be checked from the platform side (see
[Administrator troubleshooting](../administrator/troubleshooting.md) for
what that looks like internally).

## If provisioning fails outright

Failed provisioning automatically cleans up what it created — you won't be
left with a half-created, broken instance taking up your plan's quota.
Nothing about your account or billing changes when this happens; you can
retry by creating the instance again.

## If your instance is ready but the URL doesn't load yet

Domain setup happens as one of the last steps, and DNS can take a short
while to propagate even after the platform confirms it's configured. If
"Open ERP" doesn't load after a few minutes, see
[Access your ERP](../getting_started/accessing-erp.md) for what that button
actually checks before giving up.