openclaw - 💡(How to fix) Fix cron: --tz flag is silently ignored for one-shot --at jobs [1 comments, 2 participants]

1. Update the help text and option registration to clearly state that --tz only applies to --cron schedules (and error/warn when used with --at).

TL;DR

The most likely fix is to extend the parseAt(input, tz?) function to support the offset-less + --tz case for one-shots.

Guidance

• Verify the issue by checking the stored job schedule using the provided openclaw cron list --json command and comparing it to the expected schedule.
• To fix the issue, extend the parseAt(input, tz?) function in src/cli/cron-cli/shared.ts to accept an optional tz parameter and use it to parse the at input with the correct timezone offset.
• Update the register.cron-add.ts file to pass the tz option to the parseAt() function when the --at option is used.
• Consider adding error handling or warnings when the --tz option is used with --at to prevent silent failures.

Example

// In src/cli/cron-cli/shared.ts
function parseAt(input: string, tz?: string) {
  // Implement timezone-aware parsing using the provided tz parameter
  // ...
}

// In src/cli/cron-cli/register.cron-add.ts
if (at) {
  const atIso = parseAt(at, tz); // Pass tz to parseAt()
  // ...
}

Notes

The suggested fix assumes that the parseAt() function can be extended to support timezone-aware parsing. If this is not possible, updating the help text and option registration to clearly state the limitations of the --tz option may be a viable alternative.

Recommendation

Apply workaround by extending the parseAt(input, tz?) function to support the offset-less + --tz case for one-shots, as this matches user expectation and provides a more useful solution.