{"version":"2.1.247","anchor":"artifact-auto-open-stopped-storing-its-failure-banner","canonical_anchor":"artifact-auto-open-stopped-storing-its-failure-banner","heading":"Artifact auto-open stopped storing its failure banner","tier":"internal","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/artifact-auto-open-stopped-storing-its-failure-banner","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Artifact auto-open stopped storing its failure banner\n\nA failed artifact auto-open no longer leaves a banner flag behind in app state.\n\n**What**\n\nThe auto-open path no longer writes a failed-frame flag into app state, using a callback instead, and keeps only its debug log and the surfacing telemetry.\n\n**Details**\n\n- Telemetry outcomes remain `auto_open_ok` and `auto_open_failed_*`.\n- Created-from-type Artifact results now also record which auto-open mode was used.\n\n**Evidence**\n\n`frame_surfaced`\n\n- Area: Artifacts\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}