Workflows · Database schema migrations

Migration 0421 waits for the database owner before it runs in production.

Keep the migration, database target, compatibility evidence, policy decision, and execution result together.

Request a demo

Agent request

Apply migration 0421 to the production orders database

An incompatible schema change can block order writes or break the current application release.

Identity
migration-agent · Data platform
Target
production/orders
Cost
Recorded agent cost
Evidence
Migration diff, compatibility checks, and rollback statement

Policy decision

Production schema migrations require the Database owner.

Approver

Database owner

The action waits until this owner approves or denies it.

Approved

Tool call resumes

The migration tool applies the reviewed change and records its result.

Denied

Tool call stays blocked

The migration does not run and the current schema remains unchanged.

Execution order

The agent request stops before the connected tool runs.

  1. 01Migration agent requests the schema change
  2. 02Deixic checks the database, migration, evidence, and policy
  3. 03Database owner decides
  4. 04Connected database tool returns the migration result

The request, decision, recorded cost, and execution result remain in activity history.

Put this action under policy.

Request a demo.