windmill-labs/windmill · error

${stale}

Error message

${stale}

What it means

Per-item line printed after the stale-scripts header in `wmill sync push`: it is the path of one script whose metadata was found stale (info line when auto-regenerated, warn line otherwise). Not an error itself — the header message carries the guidance.

Source

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

        await flushLockfileBatch();
      }
    }
  }

  if (staleScripts.length > 0) {
    log.info("");
    if (autoRegenerate) {
      log.info("Auto-regenerated metadata for stale scripts:");
    } else {
      log.warn(
        "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 {

View on GitHub (pinned to e474e8803c)

Solutions

1. Regenerate metadata for the listed scripts via 'wmill generate-metadata'
2. Re-push so the refreshed locks are applied

When it happens

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