windmill-labs/windmill · error

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

Error message

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

What it means

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

Source

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

      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(
        "Stale apps locks found, you may want to update them using 'wmill generate-metadata' before pushing:",
      );
    }
    for (const stale of staleApps) {
      if (autoRegenerate) {
        log.info(`  ${stale}`);
      } else {
        log.warn(stale);
      }
    }
    log.info("");
  }

  // Warn about local files for skipped types. Walks the in-memory DynFSElement tree
  // (not a fresh disk scan), but does re-traverse it. Acceptable cost for a one-time check.
  {
    const skippedWarnings: string[] = [];
    let scheduleCount = 0;

View on GitHub (pinned to e474e8803c)

Solutions

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

When it happens

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