{"version":"2.1.227","anchor":"recovered-background-attaches-report-the-same-way-on-both-co","canonical_anchor":"recovered-background-attaches-report-the-same-way-on-both-co","heading":"Recovered background attaches report the same way on both code paths","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227\/e\/recovered-background-attaches-report-the-same-way-on-both-co","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.227","markdown":"### Recovered background attaches report the same way on both code paths\n\nRecovered background attaches report identically whether found by the old or new sweep.\n\n**What**\n\nThe event describing a background attach recovered from its journal moved into one shared function, so the older filesystem sweep and a new storage-backed sweep now produce identical reports.\n\n**Details**\n\n- `tengu_bg_attach_outcome` carries `journal_recovered: true`, `synthetic: true`, attach timing, first frame kind and message counts.\n\n**Evidence**\n\n`tengu_bg_attach_outcome`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5"}