NousResearch/hermes-agent · error · ValueError
Cannot resume: one-shot time {run_at} is in the past (grace
Error message
Cannot resume: one-shot time {run_at} is in the past (grace window: {ONESHOT_GRACE_SECONDS}s) and will never fire. What it means
Error "Cannot resume: one-shot time {run_at} is in the past (grace window: {ONESHOT_GRACE_SECONDS}s) and will never fire." thrown in NousResearch/hermes-agent.
Source
Thrown at cron/jobs.py:2009
{
"enabled": False,
"state": "paused",
"paused_at": _hermes_now().isoformat(),
"paused_reason": reason,
},
)
def resume_job(job_id: str) -> Optional[Dict[str, Any]]:
"""Resume a paused job and compute the next future run from now. Accepts a job ID or name."""
job = resolve_job_ref(job_id)
if not job:
return None
next_run_at = compute_next_run(job["schedule"])
if next_run_at is None and job["schedule"].get("kind") == "once":
run_at = job["schedule"].get("run_at", "unknown")
raise ValueError(
f"Cannot resume: one-shot time {run_at} is in the past "
f"(grace window: {ONESHOT_GRACE_SECONDS}s) and will never fire."
)
return update_job(
job["id"],
{
"enabled": True,
"state": "scheduled",
"paused_at": None,
"paused_reason": None,
"next_run_at": next_run_at,
},
)
def trigger_job(job_id: str) -> Optional[Dict[str, Any]]:
"""Schedule a job to run on the next scheduler tick. Accepts a job ID or name."""
job = resolve_job_ref(job_id)View on GitHub (pinned to c896c09c42)
Solutions
- Edit the job to a future run time before resuming, or create a new job.
When it happens
Trigger: Thrown at cron/jobs.py:2009 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of NousResearch/hermes-agent@c896c09c42 (2026-08-14).
Data as JSON: /api/errors/b8b46e99b394305d.
Report an issue: GitHub.