windmill-labs/windmill · error · Error

--from '${opts.from}' isn't a `// pipeline` script — it appe

Error message

--from '${opts.from}' isn't a `// pipeline` script — it appears in the local graph only as a macro consumer (lineage). Mark it `// pipeline` to run it.

What it means

Kind guard for --from in the pipeline run command: the token resolved to a script that appears in the local graph only as a macro consumer (lineage display) — a non-// pipeline DuckDB script surfaced by --local solely because it calls a macro. It has no previewable/runnable content, so starting a bounded run from it would silently produce an empty plan. The message says exactly what to change: mark the script // pipeline to make it runnable.

Source

Thrown at cli/src/commands/pipeline/pipeline.ts:751

        (r) => r.usage_kind === "script" && (r.path.split("/").pop() ?? r.path) === opts.from,
      );
      if (matches.length > 1) {
        throw new Error(
          `--from '${opts.from}' matches multiple scripts (${matches.map((r) => r.path).sort().join(", ")}) — pass the full path.`,
        );
      }
      throw new Error(`--from '${opts.from}' matched no script in f/${f}.`);
    }
    if (macroLibPaths.has(scriptPathOf(resolved))) {
      throw new Error(
        `--from '${opts.from}' is a \`// macros\` library — definition-only, injected into consuming scripts at run time, never a runnable step.`,
      );
    }
    // A `--local` display-only node (a non-`// pipeline` DuckDB script surfaced
    // only because it calls a macro) has no previewable content — reject it
    // clearly rather than admitting it and silently producing an empty plan.
    if (notRunnablePaths.has(scriptPathOf(resolved))) {
      throw new Error(
        `--from '${opts.from}' isn't a \`// pipeline\` script — it appears in the local graph only as a macro consumer (lineage). Mark it \`// pipeline\` to run it.`,
      );
    }
    if (!resolved.startsWith("script:")) {
      throw new Error(
        `--from '${opts.from}' is an asset, not a runnable — start a run from a script (assets are produced, not run).`,
      );
    }
    if (!fromEligible.has(resolved)) {
      throw new Error(
        `--from '${opts.from}' can't start a run: row-backed event triggers (kafka/mqtt/nats/postgres/sqs/gcp/email) and input-only entrypoints (webhook/data_upload) fan out per-event or need caller-supplied input — bind it with --upload to run it.`,
      );
    }
    start = resolved;
  } else if (starts.size === 1) {
    start = [...starts][0];
  } else if (starts.size === 0) {
    throw new Error(

View on GitHub (pinned to e474e8803c)

Solutions

1. Add the // pipeline tag to the script's header so it becomes a runnable pipeline step
2. Pick a different start script that is already // pipeline
3. Drop --local if you meant to run the deployed graph, where dispatch eligibility differs

When it happens

Trigger: Thrown at cli/src/commands/pipeline/pipeline.ts:751 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/67a26a8d0efe30e8. Report an issue: GitHub.