windmill-labs/windmill · error · Error
No trigger found at path: ${path}
Error message
No trigger found at path: ${path} What it means
Thrown by `wmill trigger get` when, after probing every known trigger kind (TRIGGER_TYPES) with getTrigger, no kind returned a trigger for the given path. The command tries each kind and swallows per-kind not-found errors, so this error means the trigger does not exist on the remote at all (or the path is mistyped), not that one kind rejected it.
Source
Thrown at cli/src/commands/trigger/trigger.ts:509
} else {
printTriggerDetails(trigger as any, opts.kind);
}
return;
}
// Try all trigger types and collect matches
const matches: { kind: string; trigger: any }[] = [];
for (const kind of TRIGGER_TYPES) {
try {
const trigger = await getTrigger(kind, workspace.workspaceId, path);
matches.push({ kind, trigger });
} catch {
// not found for this kind
}
}
if (matches.length === 0) {
throw new Error("No trigger found at path: " + path);
}
if (matches.length === 1) {
const { kind, trigger } = matches[0];
if (opts.json) {
console.log(JSON.stringify(trigger));
} else {
printTriggerDetails(trigger, kind);
}
return;
}
// Multiple matches — ask user to specify --kind
console.log("Multiple triggers found at path " + path + ":");
for (const m of matches) {
console.log(" - " + m.kind);
}
console.log("Please specify --kind <type> to select one.");View on GitHub (pinned to e474e8803c)
Solutions
- Run `wmill trigger list` to see existing trigger paths.
- Check the path including the folder prefix and remote (suffix-less) form.
- Recreate the trigger if it was deleted.
Defensive patterns
Strategy: fallback
When it happens
Trigger: Thrown at cli/src/commands/trigger/trigger.ts:509 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/6b41715129304b4d.
Report an issue: GitHub.