{"version":"2.1.311","anchor":"event-upload-config-key-renamed-from-joint-upload-to-event-b","canonical_anchor":"event-delivery-and-statusline-plumbing-eventbatchupload-rep","heading":"Event upload setting renamed from joint_upload to event_batch_upload","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311\/e\/event-upload-config-key-renamed-from-joint-upload-to-event-b","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.311","markdown":"### Event upload setting renamed from joint_upload to event_batch_upload\n\nThe server setting that turns on batched event uploads is now event_batch_upload, and the old joint_upload key no longer has any effect\n\n**What**\n\nClaude Code can receive a setting from the server that controls how events are uploaded in batches. That setting has been renamed:\n\n- Server field: `joint_upload` is now `event_batch_upload`. The new field is read from a different place, so the old key no longer has any effect.\n\n- Internal policy key: `jointUpload` is now `eventBatchUpload`.\n\n- Refusal check: the check for whether this upload path is refused is now its own method, `ridesAreOff()`.\n\n**Why**\n\nA server that still sends `joint_upload` will no longer turn on batched uploads. Only `event_batch_upload` does.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}