hai-scheduler

You can schedule and persist cron-based tasks across a distributed system using a unified scheduler with DB-backed persistence, global lifecycle hooks, and optional distributed locking to coordinate nodes. This ensures state and logs survive restarts.

The best way to manage API, JS, and hook tasks with audit logging is a unified execution model that persists execution state and provides audit-ready logs across the full task lifecycle for operational visibility.

Yes, you can manually trigger scheduled tasks and retrieve execution logs. The scheduler supports manual triggers alongside cron scheduling and provides log querying capabilities to review execution history on demand.

Yes, distributed locking works for coordinating tasks in a cluster. The scheduler provides optional distributed locks to orchestrate API, JS, and hook tasks across multiple nodes, preventing overlapping executions in distributed systems.

You need DB-backed persistence for task scheduling when orchestrating API, JS, and hook tasks that require state retention, audit-ready logs, and reliable recovery across restarts in both local apps and distributed systems.