Pazi's whole pitch on scheduled work is that you set it up once and trust it to run. That breaks the moment the result doesn't show up, and over the past two weeks we documented two ways it happens: the routing-inference failure and the bootstrap-latency dropout . Pazi scheduled tasks now have a three-tier delivery fallback that closes both gaps. If the configured channel disappears mid-run, the run errors before its last step, or every destination is offline, the output still reaches the dashboard. The fix covers new and existing crons, and lands alongside a new pazi-set-cron skill that asks where you want delivery before any scheduled task is created. Tier 1: resolve at creation When an agent calls cron.add , the gateway picks a delivery channel before the entry is persisted. Explicit delivery.mode: "webhook" and "none" pass through untouched. systemEvent payloads also skip the resolver, since they don't need a channel.…