windmill-labs/windmill · error

Schedule ${schedulePath} not found

Error message

Schedule ${schedulePath} not found

What it means

Thrown by `wmill schedule set-email` when the remote getSchedule call reports not-found: no schedule exists at that exact path in the workspace, typically because of a typo, wrong folder prefix, or the schedule was deleted.

Source

Thrown at cli/src/commands/schedule/schedule.ts:375

    "Set the email (run-as user) for a schedule (requires admin or wm_deployers group)"
  )
  .arguments("<path:string> <email:string>")
  .action((async (opts: any, schedulePath: string, email: string) => {
    const workspace = await resolveWorkspace(opts);
    await requireLogin(opts);

    const cache = new Map<string, { username: string; email: string }>();
    const username = await lookupUsernameByEmail(
      workspace.workspaceId,
      email,
      cache,
    );

    const remote = await wmill.getSchedule({
      workspace: workspace.workspaceId,
      path: schedulePath,
    });
    if (!remote) throw new Error(`Schedule ${schedulePath} not found`);

    await wmill.updateSchedule({
      workspace: workspace.workspaceId,
      path: schedulePath,
      requestBody: {
        ...(remote as any),
        permissioned_as: `u/${username}`,
        preserve_permissioned_as: true,
      } as any,
    });
    log.info(
      colors.green(
        `Updated permissioned_as for schedule ${schedulePath} to ${email} (username: ${username})`
      )
    );
  }) as any);

export default command;

View on GitHub (pinned to e474e8803c)

Solutions

1. Run `wmill schedule list` to see the exact remote schedule paths.
2. Check the path spelling including the u/<user>/ or f/<folder>/ prefix.
3. Recreate the schedule if it was deleted, then retry set-email.

When it happens

Trigger: Thrown at cli/src/commands/schedule/schedule.ts:375 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/b730c5125207f42a. Report an issue: GitHub.