Fix cron and scheduling tool bug in FoxFang agent

[potlock-support]

Summary

The cron / scheduling capability in the FoxFang agent is currently not working as expected and needs investigation and a fix.

Problem

There appears to be a bug affecting scheduled or cron-based task execution in FoxFang. This prevents the agent from reliably handling time-based workflows that depend on scheduled execution.

Potential symptoms may include:

• scheduled tasks not triggering at the expected time
• cron jobs failing silently
• scheduling configuration being ignored or not persisted
• reminders or recurring jobs not executing reliably
• poor visibility into whether a scheduled task was created, queued, or run

Why this matters

Scheduling is a core workflow feature for agents. If cron-based execution is broken, users cannot reliably use FoxFang for:

• reminders
• recurring checks
• periodic monitoring
• scheduled follow-ups
• automation workflows that depend on time-based execution

This reduces trust in the agent for operational and assistant workflows.

Requested fix

Investigate and fix the cron / scheduling bug so that scheduled tasks execute reliably and predictably.

Suggested areas to check

• task creation flow
• cron parsing/validation
• scheduler persistence / state recovery
• execution trigger path
• logging and error reporting for scheduled jobs
• timezone handling
• recurring vs one-shot schedule behavior

Acceptance criteria

• scheduled tasks can be created successfully
• one-time scheduled tasks run at the intended time
• recurring cron tasks run on schedule
• failures are visible in logs or status output
• timezone behavior is documented and works as expected
• users can verify whether a scheduled task is pending, executed, or failed

Context

This issue is based on practical usage where the FoxFang cron / scheduling tool was reported as not working.