Claude Code v2.1.227 ·
Rejected background dispatch files now say why
The background daemon now records why it refused a queued dispatch file.
Under the hoodTier: how much it should matter to you
2Useful: my rating, 1 to 5
2Signal: worth watching, 1 to 5
DaemonArea: what it touches
Internal ChangesKind: in v2.1.227,
Internal ChangesSection of the release
What
The background daemon records a specific reason when it refuses a queued dispatch file, so failures are distinguishable instead of silent.
Details
- Reasons:
bad_name, not_a_file, oversized, read_failed, stale, schema, bad_json, transform_throw, symlink. - A shared helper logs
[bg-dispatch] rejected … and emits tengu_bg_dispatch_rejected with a truncated reason. - A newer storage path reads dispatches with a byte cap and deletes the entry once handed off.
Evidence
daemon_bg_dispatch_ingest
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
See this entry in the whole of v2.1.227 →
