{"version":"2.1.238","anchor":"worker-client-drops-duplicate-events-and-can-treat-proxy-403","canonical_anchor":"worker-client-drops-duplicate-events-and-can-treat-proxy-403","heading":"Worker client drops duplicate events and can treat proxy 403s as transient","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/worker-client-drops-duplicate-events-and-can-treat-proxy-403","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Worker client drops duplicate events and can treat proxy 403s as transient\n\nThe background worker now drops duplicate telemetry events within an upload and logs how many.\n\n**What**\n\nThe background worker's event batcher now discards events repeating a uuid within a single upload and logs how many it dropped.\n\n**Details**\n\n- HTTP failures can carry a `nonOriginRefusal` marker, and the heartbeat streak reset skips those statuses.\n- A new constructor option `nonOrigin403Transient` decides whether such a 403 is retried; it defaults to false in this build.\n- The worker epoch is now read through a helper instead of parsing `CLAUDE_CODE_WORKER_EPOCH` inline.\n\n**Evidence**\n\n`repeated-uuid durable event(s) from one \/worker\/events POST`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}