{"version":"2.1.257","anchor":"new-unreadable-record-fallback-for-handlerscript-results","canonical_anchor":"new-unreadable-record-fallback-for-handlerscript-results","heading":"New unreadable-record fallback for handler\/script results","tier":"soon","area":"Artifacts","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257\/e\/new-unreadable-record-fallback-for-handlerscript-results","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.257","markdown":"### New unreadable-record fallback for handler\/script results\n\nHandler and script result records show as unreadable in this build rather than crashing when no renderer exists.\n\nThe session-record renderer now recognizes `handlers_doc`, `handler_result`, and `script_result` record kinds. If no renderer is registered for the current build, it shows \"This record is unreadable in this build.\" instead of crashing or showing nothing.\n\n- Area: Artifacts\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}