Database and workflow statuses
Glossary for project, deployment profile, workflow job, change, notification, CDC, and deletion states.
Parix stores several status fields because a database record, provider deployment, long-running job, dashboard change entry, and notification are different read models. Read the status in its own context.
Database project status
database.status controls project-level access, especially for shared Developer databases.
| Status | Meaning and request behavior |
|---|---|
active | Normal project access. |
inactive_warning | Inactivity warning state. Reads and writes remain allowed. |
read_only | Reads remain allowed; write operations are rejected. Used for access or billing enforcement. |
suspended | Database operations are rejected. |
pending_deletion | Database operations are rejected while the project awaits deletion handling. |
deleted | A schema-level project value, but not the normal terminal signal written by the decommission workflow. |
The current shared-project lifecycle service advances Developer rows after inactivity from active to inactive_warning at 7 days, to suspended at 14 days, and to pending_deletion at 30 days. A status change is not the same as provider-resource decommission completion.
Normal successful deletion sets the database record's soft-delete timestamp (deletedAt) and the deployment profile to deleted; customer lists filter on that timestamp. A database.status value by itself does not hide the row.
Deployment profile status
database_profile.status describes the configured provider deployment.
| Status | Meaning |
|---|---|
draft | Profile exists but has not converged into a usable deployment. |
provisioning | Provisioning or another profile-changing workflow is in progress. Configuration controls are commonly disabled. |
active | The profile is the active provider target. Gateway/data-plane requests and active-only control-plane mutations require this state. |
error | A provider or workflow step failed. Inspect the latest job and Changes view. |
deleted | The profile was decommissioned and its active routing fields were cleared. |
A project can have database.status = active while its profile is still provisioning or error. Dashboard loaders intentionally expose those non-active profiles for diagnosis even though data-plane and active-only mutations remain blocked. Use the profile and job together when diagnosing connectivity.
Provision, backup, and restore jobs
Provision, backup, and restore job records use the same core lifecycle:
| Status | Meaning |
|---|---|
queued | The request was validated, recorded, and submitted for workflow execution. |
running | The workflow has started one or more durable steps. |
completed | The job reached its success terminal state. Verify the resulting profile or artifact as well. |
failed | The job reached a failure terminal state. The record is retained for diagnosis and retry decisions. |
Import jobs add upgrading, which means the imported TigerBeetle data is passing through a required version-upgrade stage before completion.
Changes tab labels
The database Cluster → Changes read model uses presentation labels:
| Label | Interpretation |
|---|---|
Pending | Change request accepted but not yet running. |
In progress | A correlated workflow is running. |
Completed | The change reported success. |
Failed | The change reported failure. |
Change entries are written through an asynchronous log queue. They summarize workflows; they do not replace the authoritative database profile, job record, or provider state.
Notification statuses
Organization lifecycle notifications use:
queuedin_progresscompletedfailed
These are user-facing summaries and can link to the relevant database, backups page, or Changes tab. See Notifications and audit log.
CDC configuration status
CDC configuration has its own lifecycle:
| Status | Meaning |
|---|---|
draft | Configuration is stored but not active. |
queued | Apply request accepted. |
running | CDC workflow is applying provider/runtime changes. |
active | The selected configuration is active. |
error | Apply failed; inspect the CDC change and workflow detail. |
Plan and provider support still apply. An active CDC row is not evidence that a shared Developer plan exposes the CDC dashboard surface.
Deletion state
Database deletion uses a temporary decommission state:
| Status | Meaning |
|---|---|
queued | Decommission workflow has been accepted, or is waiting for active provisioning to finish. |
running | Provider and control-plane cleanup is in progress. |
failed | Cleanup stopped with a retained error message. |
On success, Parix clears this temporary state, soft-deletes the database record, and marks the profile deleted; there is no persistent completed value in the temporary decommission state.
Diagnose a database that is not ready
Check in this order:
- Project status for suspension or read-only enforcement.
- Temporary deletion state.
- Deployment profile status.
- Latest provision, import, backup, restore, or upgrade job.
- The Changes tab and linked notification.
- Gateway health only after the profile is
active.
This order avoids treating a notification or stale change entry as the current provider truth.