Provisioning and database status
Understand shared activation, dedicated provisioning, dashboard status, and retries.
Database creation has two lifecycle shapes. A Developer shared database is placed into an existing shared cell and becomes active immediately. A dedicated database creates a profile and runs an asynchronous provisioning job before it is ready.
Dedicated profile states
| Profile state | Meaning |
|---|---|
draft | The requested profile exists but provisioning has not started. |
provisioning | Infrastructure is being created or changed. Operations that require an active profile remain unavailable. |
active | The profile is operational. The dashboard shows Ready when no higher-priority lifecycle state applies. |
error | Provisioning or a later control-plane change failed. Review the displayed error before retrying. |
deleted | Teardown completed and the retained profile is lifecycle history. The database is hidden from normal product routes. |
The provisioning job has its own status:
| Job status | Meaning |
|---|---|
queued | The durable provisioning workflow has been accepted but has not started work. |
running | Provider resources and Parix routing are being configured. |
completed | The job completed and the profile should be active. |
failed | The job stopped with an error. |
Status shown on the dashboard
The dashboard combines provisioning and deletion state into a user-facing label:
| Dashboard label | Source state |
|---|---|
| Not provisioned | No provisioning job or profile status is available. |
| Provisioning | Job is queued or running, or profile is provisioning. |
| Ready | Job is completed or profile is active. |
| Error | Job is failed or profile is error. |
| Deleting | Deletion is queued or running; this takes precedence over provisioning. |
| Delete failed | The deletion workflow failed. |
The organization-level Recent databases list does not show provisioning progress. It normally labels a database Active until deletion begins. Open the database dashboard for the effective provisioning label and error details.
Follow progress
Use these surfaces together:
- Open the database dashboard to read the current label and any provisioning error.
- Select the notification bell to follow queued, in-progress, completed, or failed lifecycle notifications.
- Refresh the database page if a workflow has just transitioned.
When provisioning fails and a profile is available, the dashboard offers Try Again. Review the error before retrying; repeated failures can indicate unavailable provider capacity or configuration that requires support.
Concurrent lifecycle operations
Parix prevents conflicting work. An active deletion blocks new provisioning or upgrades. If deletion is requested while dedicated provisioning is already active, deletion remains queued and starts only after provisioning finishes. See Delete a database for the deferred state.