Scheduler

The Laravel scheduler is the time-driven entry point to Kraite's workload. Every recurring job — kline fetches, indicator computation, listenKey refreshes, balance snapshots, candle purges, audit-log retention — flows through routes/console.php on ingestion.kraite.com, running on Kraite. The scheduler does not execute trading logic itself; it dispatches into the dispatch daemon and the Horizon queues, which do the work.

This is the subsystem lens view. For the persistent process that replaced one specific scheduled command (steps:dispatch), see Dispatch daemon.

The cron table

The hourly direction-conclusion command also owns an application lock, so a manual run and the scheduled run cannot overlap. Its destructive --clean mode is accepted only in local or testing; production refuses the flag before deleting any indicator or direction data.

The split symbol schedule keeps catalogue, token, and availability data fresh every hour without sending a full per-symbol leverage sweep into the cron lane each time. The six-hour run is explicit and manually reproducible; normal hourly runs create zero leverage-bracket steps.

What "cooldown-gated" means

routes/console.php registers step-producing commands only while the Kraite singleton reports is_cooling_down=false. During a release those entries disappear from the schedule, so they cannot create fresh work while queues drain. Recovery, listen-key maintenance, health, and backups stay registered. withoutOverlapping() is a separate Laravel mutex that prevents two instances of one command from running concurrently.

                tick fires
                    │
                    ▼
            ┌────────────────────┐
            │ System cooling down?│── yes ─► entry not registered
            └─────────┬──────────┘
                    no
                    ▼
            ┌────────────────────┐
            │ withoutOverlapping │── busy ► skip this tick
            │       mutex        │
            └─────────┬──────────┘
                    ok
                    ▼
              run command
                    │
                    ▼
             release mutex

Maintenance mode silences everything — and its sentinel

The scheduler skips every event while the application is in maintenance mode. That is by design during a deploy (cooldown parks each box in maintenance; warmup lifts it) — but it means a box accidentally left in maintenance loses its entire cron table silently: listenKey keepalive, sync fallback, database backups, and every watchdog, all at once, while supervisors and Horizon still look healthy.

Since then, the health watchdog (kraite:cron-check-system-health) is the one scheduled command that runs even in maintenance mode. While the box is down it performs a single check — "has this box been in maintenance longer than the threshold" (default 45 minutes, sized above a full cooldown → deploy → warmup span) — and pages CRITICAL on breach, re-paging every 30 minutes until an operator brings the box up. The full check pass stays skipped during maintenance, so normal deploy windows never produce transient alerts. The release runbooks carry the matching gates: warmup hard-verifies the box answers "UP" after warming, and the fleet health grid renders a Maint column that fails on any leftover maintenance marker.

Recovery after warmup

Warmup starts Horizon and the daemons before it resumes the scheduler on the same host. It then starts a 10-minute recovery grace for the two health signals produced through the default dispatcher: account-balance history and indicators. Those timestamps can still describe the pre-deploy state until the first producer jobs finish.

The grace does not mute mark prices, queues, Redis, the database, daemons, scheduler liveness, or fleet heartbeats. Indicator freshness also checks the exact symbol's producer workflow: a recent query or conclusion in progress is an active repair, while terminal work or an abandoned old step cannot suppress a real alert.

Copied exchange symbols also defer to their fresh Binance source. A delayed copy is not paged while the same token and quote has fresh native analysis; when the Binance source is stale, the source alert remains visible.

Why a daemon replaced steps:dispatch

Cross-lens links

• Dispatch daemon — the persistent loop that took over from steps:dispatch
• Kraite host — where this scheduler runs
• Horizon queues — where every dispatched job lands