Provisioning and configuration

Configuration requests are workflow-backed. The browser validates the request and queues a provider workflow; it does not mutate infrastructure directly.

Use this page when a create, import, upgrade, topology, storage, parameter, or CDC action is rejected before a workflow starts.

Create or import is blocked

Check:

• organization billing is ready
• database name is unique in the organization
• selected provider, region, topology, storage tier, storage size, and cluster size exist in the catalog
• import files form a complete replica set
• imported TigerBeetle version is not newer than the supported target

Fix: correct the failed prerequisite, then resubmit. A blocked create request should not leave a partially provisioned database unless the API response explicitly includes database or job data.

Configuration action is disabled

Most configuration actions require an active database profile. If the profile is still provisioning, Parix blocks new topology, storage, parameter, CDC, backup, and restore changes.

Fix: wait for the current workflow to finish, then retry from the same dashboard tab.

No changes to queue

The cluster, storage, and parameter routes compare submitted values with the active profile. If the effective selection is unchanged, the route skips workflow creation and reports that there are no changes to queue.

Provider limits

Current provider-specific limits include:

• GCP topology changes use backup-driven migration and controlled downtime.
• GCP storage changes can only increase disk size.
• AWS topology and storage changes are blocked until restore-backed migration exists for AWS.
• GCP and AWS local NVMe deployments block several post-create storage and topology changes in the current product version.
• Parameter changes are supported only for GCP deployments.

Upgrade behavior

Version upgrades and other in-place changes move the profile into provisioning while the workflow runs. Check the Cluster Changes tab for durable change outcomes.