windmill-labs/windmill · error

Stale flows locks found, you may want to update them using '

Error message

Stale flows locks found, you may want to update them using 'wmill generate-metadata' before pushing:

What it means

Post-push advisory in `wmill sync push`: flow locks were detected as stale (flow definition changed since its lock was generated) and autoRegenerate was off. The following lines list the affected flow paths; the push itself completed.

Source

Thrown at cli/src/commands/sync/sync.ts:5191

        "Stale scripts metadata found, you may want to update them using 'wmill generate-metadata' before pushing:",
      );
    }
    for (const stale of staleScripts) {
      if (autoRegenerate) {
        log.info(`  ${stale}`);
      } else {
        log.warn(stale);
      }
    }

    log.info("");
  }

  if (staleFlows.length > 0) {
    if (autoRegenerate) {
      log.info("Auto-regenerated locks for stale flows:");
    } else {
      log.warn(
        "Stale flows locks found, you may want to update them using 'wmill generate-metadata' before pushing:",
      );
    }
    for (const stale of staleFlows) {
      if (autoRegenerate) {
        log.info(`  ${stale}`);
      } else {
        log.warn(stale);
      }
    }
    log.info("");
  }

  if (staleApps.length > 0) {
    if (autoRegenerate) {
      log.info("Auto-regenerated locks for stale apps:");
    } else {
      log.warn(

View on GitHub (pinned to e474e8803c)

Solutions

  1. Run 'wmill generate-metadata' to refresh flow locks
  2. Push again after regeneration so remotes carry current locks
Defensive patterns

Strategy: fallback

When it happens

Trigger: Thrown at cli/src/commands/sync/sync.ts:5191 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/a009f64b7ba24a0a. Report an issue: GitHub.