Use case

Cron jobs for scripts that need more than a function

Some jobs are too long for a serverless function and too small to deserve a server.

The problem

A cron entry on a server you do not look after fails quietly. A function with a short timeout cannot finish the work.

What NeverHalt gives you

• Run history

  Every run is listed with its status, duration and exit code.

• A disk that survives restarts

  Every agent gets its own /app/data folder. SQLite files, checkpoints and caches are still there after a crash, a redeploy or a restart.

• You see what it does

  Live logs, plus an activity log of AI calls, tool calls and errors with token counts and cost.

• Secrets stay secret

  API keys are encrypted at rest and injected into the process. Your real AI key can stay with NeverHalt and never enter the agent.

Cron schedule

execution_mode: cron
cron_schedule: "0 6 * * *"   # every day at 06:00 UTC

Questions

What time zone does the schedule use?

UTC.