{"version":"2.1.261","anchor":"wakerouter-now-retries-failed-agent-wake-dispatches-instead","canonical_anchor":"wakerouter-now-retries-failed-agent-wake-dispatches-instead","heading":"wakeRouter now retries failed agent-wake dispatches instead of dropping them","tier":"notice","area":"Background Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261\/e\/wakerouter-now-retries-failed-agent-wake-dispatches-instead","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.261","markdown":"### wakeRouter now retries failed agent-wake dispatches instead of dropping them\n\nFailed wake-ups to background agents are now retried with backoff instead of silently dropped.\n\nThe background wake dispatcher that delivers queued commands to agents no longer drops a delivery on the first failure. It now classifies each outcome as delivered, dropped, or retry: non-terminal failures (not an abort\/stop error, and under a retry cap) are rescheduled with jittered exponential backoff using a new per-agent timer map. Commands are only dropped, with a new `resume_failed` reason, once an error isn't retryable or the retry-count cap is reached.\n\n- Area: Background Agents\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}