windmill-labs/windmill · error

Failed to run deployed migrations: ${e}

Error message

Failed to run deployed migrations: ${e}

What it means

Degradation near the end of `wmill workspace merge`: items including migration definitions were deployed, but the follow-up offerToRunNewMigrations on the target workspace threw (API error, canceled prompt, or migration execution failure). Deployment succeeded; only running the migrations on the target was skipped.

Source

Thrown at cli/src/commands/workspace/merge.ts:644

      )
    );
  } else {
    log.info(
      colors.yellow(
        `Deployed ${successCount} item(s), ${colors.red(String(failCount) + " failed")} from ${workspaceFrom} to ${workspaceTo}.`
      )
    );
  }

  // 13. Deployed migration definitions don't touch the target schema until run;
  // offer to run them on the target now (interactive only, like the push path).
  if (deployedMigrations.length > 0) {
    try {
      await offerToRunNewMigrations(workspaceTo, deployedMigrations, {
        yes: opts.yes,
      });
    } catch (e) {
      log.warn(colors.yellow(`Failed to run deployed migrations: ${e}`));
    }
  }
}

export { mergeWorkspaces };

View on GitHub (pinned to e474e8803c)

Solutions

1. Run the deployed migrations on the target workspace manually via the UI or CLI
2. Inspect the wrapped error `e` for the actual migration failure
3. Re-run the merge or use the migrations run command once the cause is fixed

When it happens

Trigger: Thrown at cli/src/commands/workspace/merge.ts:644 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of windmill-labs/windmill@e474e8803c (2026-09-03). Data as JSON: /api/errors/3b6dbbb08bd25dd8. Report an issue: GitHub.