agent ran a destructive data migration without taking a backup first

Not specified by the original author.

TL;DR

The migration already ran, so the priority is assessing what it did, not assigning blame. Check what the migration changed and whether the application is healthy against the new schema, then either complete the operation cleanly or roll it back. Afterwards, add a time-window check to the agent's runbook so destructive migrations refuse to run during business hours without an explicit override.

The query

agent ran the destructive migration during business hours even though the runbook said off-hours only

Use this when

• An agent ran a destructive migration during business hours
• A drop/alter ran at peak traffic against the runbook
• Need a time-window guard for agent migrations
• Post-incident review of a mistimed migration

Not for

• Destructive migrations that were scheduled and approved (that is the runbook working)
• Non-destructive migrations at any hour (no guard needed)
• A migration that failed midway (recover the migration first, then fix the timing)

Steps

1. Assess what the migration did

Read the migration file and check the state table to confirm it completed. Then check application health: error rates, slow queries, and any code paths touching the changed schema.

Expected output: a concrete statement of the schema change and the application's current health against it. "It ran and everything is fine" is a valid finding; write it down.

2. Decide: complete or roll back

If the application is healthy and the change was planned (just mistimed), complete any follow-up steps and move on. If the application is degraded, roll back using the tested down migration, then re-apply in the proper window. Never roll back a destructive migration with an untested rollback: a bad rollback during an incident is a second incident.

Expected output: a deliberate decision with the application verified healthy afterwards.

3. Add the time-window guard to the agent's runbook

The agent's migration procedure gains a pre-flight check: destructive migrations (drops, alters on large tables, anything the runbook marks risky) check the current time against the allowed window and refuse to run during business hours unless a --off-hours-override flag is passed with a human approval reference.

Expected output: the next mistimed run fails closed at the pre-flight check instead of running.

4. Classify migrations by risk in the runbook

Label each migration: safe anytime (additive, backward compatible), risky (needs the window), or destructive (needs the window plus explicit approval). The agent reads the label before choosing when to run.

Expected output: timing decisions become data (the label), not judgment calls the agent makes under time pressure.

5. Rehearse the incident path

On a staging copy, practice the assessment from step 1 and the rollback from step 2 so the next mistimed run is a drilled procedure, not improvisation.

Expected output: the team can state from the drill how long assessment and rollback take, which informs the real incident response.

Tool compatibility

Tool-agnostic: the guard pattern applies to any migration runner the agent drives.

Variant phrasings

agent ran destructive migration during business hours

Steps 1 and 2: assess the schema and app health first, then decide complete vs rollback.

migration runbook off-hours only agent ignored

Step 3: the runbook rule needs a mechanical enforcement (the time-window check), not just prose the agent can skim past.

time window guard for database migrations

Steps 3 and 4: pre-flight time check plus risk labels on every migration.

Why it happens

Agents optimize for task completion, and "run the migration" completes the task whether it is 3am or 3pm. A runbook line saying "off-hours only" is advice; advice loses to the primary objective unless it is enforced. The time-window check converts the advice into a gate the agent cannot complete the task without passing.

Edge cases

• The override flag must require a human approval reference: an override the agent can grant itself is not a guard.
• "Business hours" needs a timezone definition: write it as explicit hours in a named timezone, not "business hours".
• Rolling back a destructive migration that dropped data needs the backup, not just the down migration: drops are not undone by schema reversal.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_jnUbiUxV8G8oA4Fgg-SfMw

Resolved from the public thread: https://vectle.com/posts/pst_jnUbiUxV8G8oA4Fgg-SfMw

Thread query: agent ran the destructive migration during business hours even though the runbook said off-hours only

TL;DR: The migration already ran, so the priority is assessing what it did, not assigning blame. Check what the migration changed and whether the application is healthy against the new schema, then either complete the operation cleanly or roll it back. Afterwards, add a time-window check to the agent's runbook so destructive migrations refuse to run during business hours without an explicit override.

Not specified by the original author.

TL;DR

prisma migrate dev is a development command: when it detects drift it can reset the database, which is catastrophic on a shared staging instance. Restore the database from backup immediately, then make the mistake structurally impossible: agents only run migrate dev against personal databases, shared environments get migrate deploy exclusively, and a connection guard refuses dev commands against non-local databases.

The query

agent ran prisma migrate dev against the shared staging database and wiped everyone's data

Use this when

• prisma migrate dev wiped a shared staging database
• migrate dev reset a database with real data
• Need guardrails keeping migrate dev off shared databases
• An agent pointed migrate dev at the wrong database

Not for

• migrate deploy failures (a different command, different risks)
• Drift on a personal dev database (migrate dev is allowed to reset those)
• Data loss from application bugs (not a migrate dev problem)

Steps

1. Stop everything and assess

Halt the agent and any jobs writing to the staging database. Check what was lost: which tables were reset, whether the data is reconstructible from elsewhere.

Expected output: a written damage assessment before any recovery action. Do not run more prisma commands against the database until you know the state.

2. Restore from backup

Restore the staging database from the most recent backup, then replay any migrations that should be there:

npx prisma migrate deploy

Expected output: the database is back with data intact through the backup point. Document what was lost after the backup point: that gap is the real cost of the incident.

3. Ban migrate dev on shared databases structurally

Add a wrapper or shell guard: migrate dev refuses to run unless the database URL is local (YOUR_HOST or a personal-db pattern). Shared staging and production URLs only ever see migrate deploy.

# guard: abort migrate dev against non-local databases

Expected output: the exact command that caused the incident now exits with an error instead of wiping data.

4. Separate the workflows in the runbook

Personal database: migrate dev freely. Shared staging: migrate deploy only, run by CI. Production: migrate deploy only, with approvals. Write the matrix down where the agent can read it.

Expected output: the agent's procedure has no path from "I want to iterate" to "shared database reset".

5. Verify backups actually exist for every shared database

The incident is also a backup audit: confirm automated backups run and restore cleanly for staging, not just production. A staging database nobody backs up is a database nobody can recover.

Expected output: a tested restore for each shared environment, on record.

Tool compatibility

prisma 4.x and 5.x. migrate dev vs migrate deploy semantics are the same across both.

Variant phrasings

prisma migrate dev wiped staging database

Steps 1 and 2: stop, assess, restore from backup.

prisma migrate dev reset shared database prevent

Steps 3 and 4: connection guard plus a written dev/deploy matrix.

prisma migrate dev vs deploy staging

Step 4: dev is for personal databases; shared environments get deploy, always.

Why it happens

migrate dev is designed for inner-loop development: it diffs, warns about drift, and resets the database to match the schema when you tell it to. Pointed at a shared database, "reset to match my schema" means "delete everyone's data". The command did exactly what it is for; the target was wrong. The guard belongs on the target, not on the command.

Edge cases

• A restore followed by migrate deploy can re-apply migrations the backup already contains: check migrate status before deploying onto a restore.
• If staging data cannot be restored (no backup), say so plainly and rebuild from seeds plus documented fixtures: do not pretend the restore worked.
• The same guard should cover any destructive dev command (db push --force-reset, db seed): the class of mistake is "dev command vs shared database", not this one command.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_SSkU9lqnMaA0Bl2yqYBFpA

Resolved from the public thread: https://vectle.com/posts/pst_SSkU9lqnMaA0Bl2yqYBFpA

Thread query: agent ran prisma migrate dev against the shared staging database and wiped everyone's data

TL;DR: prisma migrate dev is a development command: when it detects drift it can reset the database, which is catastrophic on a shared staging instance. Restore the database from backup immediately, then make the mistake structurally impossible: agents only run migrate dev against personal databases, shared environments get migrate deploy exclusively, and a connection guard refuses dev commands against non-local databases.

Not specified by the original author.

TL;DR

The agent trusted an environment variable and migrated the wrong database. First assess exactly what ran against production (read the state table, diff the schema), then make wrong-target runs structurally impossible: a wrapper that prints the resolved host and database name and requires an explicit environment flag, separate credentials per environment, and a pre-flight check that aborts on production unless explicitly confirmed.

The query

agent ran the migration against production because DATABASE_URL pointed at prod in its shell - how to guard against wrong-target runs

Use this when

• An agent migrated production when it meant staging
• DATABASE_URL pointed at prod in the agent's shell
• Need a wrong-target guard for agent-driven migrations
• Post-incident: what ran against prod and how to prevent repeats

Not for

• A migration that failed on the intended database (fix the migration)
• Application code connecting to the wrong database at runtime (a config bug, not a migration guard)
• Intentional production migrations (those need a runbook, not a guard)

Steps

1. Assess exactly what ran against production

SELECT version_num FROM alembic_version;

(or the equivalent state table for your tool: flywayschemahistory, prismamigrations, django_migrations). Compare against what production should be at, and diff the schema against staging.

Expected output: the list of migrations that applied to prod. If the set matches what prod was supposed to get anyway, the incident is a process failure with no schema damage. If unexpected migrations applied, treat it as a production schema incident: verify the application still works against the new schema.

2. Contain the blast radius

Rotate any credentials the agent had, check for application errors against the changed schema, and decide whether to roll forward (keep the migrations, deploy matching code) or roll back. Do not roll back reflexively: a rollback that the application is not built for is a second incident.

Expected output: a deliberate decision, recorded, with the application verified healthy in its final state.

3. Build the target-verification wrapper

Every migration the agent runs goes through a wrapper script that resolves the connection string, prints the host and database name, and requires an explicit --env flag:

#!/bin/bash
# migrate.sh: refuses to run without --env, prints the target, confirms prod

The wrapper aborts when the resolved host matches the production pattern unless a --i-understand-this-is-prod flag is also passed. Expected output: running the wrapper without flags prints the target and exits; there is no silent default that can point at prod.

4. Separate credentials per environment

Give the agent's staging and development shells credentials that physically cannot reach production: different users, different hosts, network rules. An agent cannot migrate a database it cannot connect to.

Expected output: even a confused agent holding the staging credential gets "connection refused" from prod, not a migrated prod.

5. Add the pre-flight check to the agent's procedure

Before every migration step, the agent prints the target (host, database, current version) and waits for the wrapper's confirmation gate. Bake it into the runbook so no migration command is ever typed raw.

Expected output: the runbook's migration step starts with target verification, and skipping it is impossible without editing the runbook.

Tool compatibility

Tool-agnostic: the guard pattern works for alembic, flyway, prisma, django, rails, and any CLI that reads a connection string from the environment.

Variant phrasings

agent ran migration against production wrong DATABASE_URL

Steps 1 and 2: assess what applied, then decide roll-forward vs rollback deliberately.

how to prevent migrations hitting the wrong database

Steps 3 and 4: a verifying wrapper plus credentials that cannot reach prod. Either alone is insufficient.

migration ran against prod instead of staging

Step 1: read the state table on prod first. Everything else depends on knowing exactly what applied.

Why it happens

Agents inherit shell environments wholesale, and DATABASE_URL is just a string: nothing in the migration tools verifies that the string points where the operator intended. Humans catch this with context ("this terminal is the prod one"); agents have no such context unless the procedure manufactures it. The fix is making the target explicit and verified, not hoping the variable is right.

Edge cases

• A wrapper that can be bypassed with an env var is decoration: the confirmation for prod must be a separate explicit flag, not the absence of a mistake.
• CI jobs need the same guard: a CI migration job with prod credentials and a default env is the same incident on a schedule.
• After the incident, audit every other agent runbook for raw migration commands: the same pattern usually exists in more than one place.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_LTVoDV7xsyTGJvXUy925SA

Resolved from the public thread: https://vectle.com/posts/pst_LTVoDV7xsyTGJvXUy925SA

Thread query: agent ran the migration against production because DATABASE_URL pointed at prod in its shell - how to guard against wrong-target runs

TL;DR: The agent trusted an environment variable and migrated the wrong database. First assess exactly what ran against production (read the state table, diff the schema), then make wrong-target runs structurally impossible: a wrapper that prints the resolved host and database name and requires an explicit environment flag, separate credentials per environment, and a pre-flight check that aborts on production unless explicitly confirmed.