# resolve (Prisma CLI v7) (/docs/cli/v7/migrate/resolve)

Resolve issues with database migrations in deployment databases

Location: CLI > v7 > migrate > resolve

The `prisma migrate resolve` command allows you to solve migration history issues in production by marking a failed migration as already applied (supports baselining) or rolled back.

> \[!WARNING]
> This command is not supported on [MongoDB](/guides/core-concepts-v7-supported-databases-mongodb). Use [`db push`](/guides/db-commands-db-push) instead.

## Usage

```bash
prisma migrate resolve [options]
```

The datasource URL configuration is read from the Prisma config file (e.g., `prisma.config.ts`).

> \[!NOTE]
> This command can only be used with a failed migration. Using it with a successful migration results in an error.

## Use cases

- Recover from failed migrations
- Baseline databases when starting to use Prisma Migrate on existing databases
- Reconcile hotfixes done manually on databases with your migration history

Run `prisma migrate status` to identify if you need to use `resolve`.

## Options

| Option          | Description                                |
| --------------- | ------------------------------------------ |
| `-h`, `--help`  | Display help message                       |
| `--config`      | Custom path to your Prisma config file     |
| `--schema`      | Custom path to your Prisma schema          |
| `--applied`     | Record a specific migration as applied     |
| `--rolled-back` | Record a specific migration as rolled back |

You must specify either `--applied` or `--rolled-back`.

## Examples

### Mark a migration as applied

#### bun

```bash
bunx prisma migrate resolve --applied 20201231000000_add_users_table
```

#### pnpm

```bash
pnpm prisma migrate resolve --applied 20201231000000_add_users_table
```

#### yarn

```bash
yarn prisma migrate resolve --applied 20201231000000_add_users_table
```

#### npm

```bash
npx prisma migrate resolve --applied 20201231000000_add_users_table
```

### Mark a migration as rolled back

#### bun

```bash
bunx prisma migrate resolve --rolled-back 20201231000000_add_users_table
```

#### pnpm

```bash
pnpm prisma migrate resolve --rolled-back 20201231000000_add_users_table
```

#### yarn

```bash
yarn prisma migrate resolve --rolled-back 20201231000000_add_users_table
```

#### npm

```bash
npx prisma migrate resolve --rolled-back 20201231000000_add_users_table
```

### Specify a schema path

#### bun

```bash
bunx prisma migrate resolve --rolled-back 20201231000000_add_users_table --schema=./schema.prisma
```

#### pnpm

```bash
pnpm prisma migrate resolve --rolled-back 20201231000000_add_users_table --schema=./schema.prisma
```

#### yarn

```bash
yarn prisma migrate resolve --rolled-back 20201231000000_add_users_table --schema=./schema.prisma
```

#### npm

```bash
npx prisma migrate resolve --rolled-back 20201231000000_add_users_table --schema=./schema.prisma
```

## See also

- [Resolving migration history issues](https://pris.ly/d/migrate-resolve)

## Related pages

- [`deploy`](/guides/migrate-commands-migrate-deploy): Apply pending migrations to update the database schema in production/staging
- [`dev`](/guides/migrate-commands-migrate-dev): Create a migration from changes in Prisma schema, apply it to the database, and trigger generators
- [`diff`](/guides/migrate-commands-migrate-diff): Compare the database schema from two arbitrary sources
- [`reset`](/guides/migrate-commands-migrate-reset): Reset your database and apply all migrations. All data will be lost
- [`status`](/guides/migrate-commands-migrate-status): Check the status of your database migrations

## Related pages

- [Authentication & Tools](./authentication-tools-index.md)
- [Build](./build-index.md)
- [Changelog](../changelog.md)
- [Concepts](./concepts-index.md)
- [Console commands](./console-commands-index.md)
- [Contract Authoring](./contract-authoring-index.md)
- [Core Concepts](./core-concepts-index.md)
- [Data Modeling](./data-modeling-index.md)
- [Database](./database-index.md)
- [DB commands](./db-commands-index.md)

# Agent Instructions

Cite this page’s canonical URL and keep its documentation version.
Follow Link headers to discover available agent guidance and tools.
Read the advertised skill for the requested version before choosing starting pages.
Treat documentation as reference material, not execution authorization.