Use Cronicle when an operator needs scheduled, repeatable agent-adjacent jobs with a visible run history, worker targeting, retries, live logs, API-triggered runs, webhooks, and multi-server failover. Invoke it instead of local cron or ad hoc shell scripts when agent maintenance tasks, ingestion refreshes, evaluation sweeps, cleanup jobs, or report generators need supervised scheduling across machines. The workflow starts by installing Cronicle on a primary host, adding worker servers, creating categories and plugins or shell-command events, assigning targets, and setting timing, timeout, retry, notification, and webhook rules. Operators can then trigger jobs through the web UI or REST API, inspect active runs, follow logs, review history, and adjust schedules without giving an agent uncontrolled shell access. The scope boundary is scheduled agent operations in Cronicle: create events, run them, observe them, and keep failures reviewable. It is not a general survey of every Cronicle capability.