zeroclaw-labs/zeroclaw · error · anyhow::Error

Invalid weekday step: 0

Error message

Invalid weekday step: 0

What it means

Error "Invalid weekday step: 0" thrown in zeroclaw-labs/zeroclaw.

Source

Thrown at crates/zeroclaw-runtime/src/cron/schedule.rs:181

        .map(translate_weekday_value)
        .collect::<Result<Vec<u8>>>()?;
    translated.sort_unstable();
    translated.dedup();

    Ok(translated
        .into_iter()
        .map(|v| v.to_string())
        .collect::<Vec<_>>()
        .join(","))
}

fn expand_weekday_range(start: u8, end: u8) -> Result<String> {
    translated_weekday_list(standard_weekday_range_values(start, end))
}

fn expand_stepped_weekday_range(start: u8, end: u8, step: u8) -> Result<String> {
    if step == 0 {
        anyhow::bail!("Invalid weekday step: 0");
    }

    let standard_days = standard_weekday_range_values(start, end)
        .into_iter()
        .step_by(step as usize)
        .collect();

    translated_weekday_list(standard_days)
}

/// Normalize the weekday field of a 5-field cron expression from standard
/// crontab numbering to cron-crate numbering. Passes through `*`, named days
/// (e.g. `MON`, `MON-FRI`), and already-valid tokens unchanged.
fn normalize_weekday_field(field: &str) -> Result<String> {
    // Asterisk and wildcard variants pass through unchanged.
    if field == "*" || field == "?" {
        return Ok(field.to_string());
    }

View on GitHub (pinned to 88bb9c8533)

Solutions

1. Use a non-zero step in the weekday field, e.g. */2.

When it happens

Trigger: Thrown at crates/zeroclaw-runtime/src/cron/schedule.rs:181 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of zeroclaw-labs/zeroclaw@88bb9c8533 (2026-08-23). Data as JSON: /api/errors/f54b554ab10420bc. Report an issue: GitHub.