nexu-io/open-design · error · Error

--schedule weekly day must be 0-6 or sun..sat (got "${parts[

Error message

--schedule weekly day must be 0-6 or sun..sat (got "${parts[1]}")

What it means

Thrown by parseScheduleFlag for a weekly schedule when the day token is neither a single digit 0-6 nor a recognized entry in AUTOMATION_WEEKDAY_TOKENS (the sun/mon/tue/wed/thu/fri/sat map). The token is lowercased first, so case does not matter, but the value must be one of those exact abbreviations or a 0-6 digit.

Source

Thrown at apps/daemon/src/cli.ts:10529

    const time = `${hh.padStart(2, '0')}:${mm.padStart(2, '0')}`;
    if (!/^[0-2]\d:[0-5]\d$/.test(time)) {
      throw new Error(`--schedule ${kind} time must be HH:MM (24h)`);
    }
    const timezone = parts.slice(3).join(':') || 'UTC';
    return { kind, time, timezone };
  }
  if (kind === 'weekly') {
    if (parts.length < 4) {
      throw new Error('--schedule weekly requires :DAY:HH:MM[:TZ] (DAY is 0-6 or sun/mon/...)');
    }
    const dayToken = String(parts[1]).toLowerCase();
    let weekday;
    if (/^[0-6]$/.test(dayToken)) {
      weekday = Number(dayToken);
    } else if (AUTOMATION_WEEKDAY_TOKENS[dayToken] !== undefined) {
      weekday = AUTOMATION_WEEKDAY_TOKENS[dayToken];
    } else {
      throw new Error(`--schedule weekly day must be 0-6 or sun..sat (got "${parts[1]}")`);
    }
    const time = `${parts[2].padStart(2, '0')}:${parts[3].padStart(2, '0')}`;
    if (!/^[0-2]\d:[0-5]\d$/.test(time)) {
      throw new Error('--schedule weekly time must be HH:MM (24h)');
    }
    const timezone = parts.slice(4).join(':') || 'UTC';
    return { kind: 'weekly', weekday, time, timezone };
  }
  throw new Error(`--schedule kind must be hourly|daily|weekdays|weekly (got "${kind}")`);
}

function parseAutomationTarget(flags) {
  const raw = flags.target;
  if (raw == null) {
    if (flags.project) return { mode: 'reuse', projectId: String(flags.project) };
    return { mode: 'create_each_run' };
  }
  const value = String(raw);

View on GitHub (pinned to 5be4028344)

Solutions

  1. Use a digit 0-6 where 0 is Sunday, e.g. `--schedule weekly:1:09:30` for Monday.
  2. Or use the three-letter lowercase abbreviation, e.g. `--schedule weekly:mon:09:30`.
  3. Avoid full names like 'Monday' and 1-based 1-7 numbering.

Example fix

// before
--schedule weekly:Monday:09:30
// after
--schedule weekly:mon:09:30
Defensive patterns

Strategy: validation

Validate before calling

const WEEKDAY_TOKENS = ['sun','mon','tue','wed','thu','fri','sat'];
function isValidWeeklyDay(token: string): boolean {
  const t = token.toLowerCase();
  return /^[0-6]$/.test(t) || WEEKDAY_TOKENS.includes(t);
}

Try / catch

try {
  parseScheduleFlag(raw);
} catch (err) {
  if (err instanceof Error && /weekly day must be 0-6 or sun..sat/.test(err.message)) {
    // re-prompt for a valid day token
  }
  throw err;
}

Prevention

When it happens

Trigger: Running `--schedule weekly:8:09:30` (digit out of 0-6), `--schedule weekly:Monday:09:30` (full name, not the 3-letter token), `--schedule weekly:funday:09:30`, or `--schedule weekly:7:09:30` (1-based indexing).

Common situations: Using full weekday names ('monday'), 1-based day numbers (1-7), or a typo in the abbreviation. The accepted tokens are 0-6 (0 = Sunday) or the three-letter sun..sat forms.

Related errors

AI-assisted analysis of nexu-io/open-design@5be4028344 (2026-08-12). Data as JSON: /api/errors/e7b9b36be06aff0f. Report an issue: GitHub.