{"version":"2.1.222","anchor":"bridge-attestation-warnings-are-reported-once-per-event","canonical_anchor":"bridge-attestation-warnings-are-reported-once-per-event","heading":"Bridge attestation warnings are reported once per event","tier":"notice","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222\/e\/bridge-attestation-warnings-are-reported-once-per-event","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.222","markdown":"### Bridge attestation warnings are reported once per event\n\nA failing device attestation now warns you once instead of spamming repeated notices.\n\n**What**\n\nThe attestation notice emitter now keys on event_id and skips events it has already reported, so a single bad event no longer produces repeated warnings.\n\n**Details**\n\n- The set of seen event ids is bounded.\n- The hint about re-pairing a device is no longer restricted to control_request payloads and now shows for any attestation failure.\n- A drop-sender notice writer is registered on the remote-io transport and unregistered when it closes.\n\n**Evidence**\n\n`Re-pair the sending device in Trusted Devices.`\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 0\/5"}