{"version":"2.1.242","anchor":"a-malformed-pasted-item-no-longer-discards-a-history-line","canonical_anchor":"a-malformed-pasted-item-no-longer-discards-a-history-line","heading":"A malformed pasted item no longer discards a history line","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/a-malformed-pasted-item-no-longer-discards-a-history-line","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### A malformed pasted item no longer discards a history line\n\nA single bad pasted-content record no longer throws away the whole history entry.\n\n**What**\n\nCommand history lines are now validated against a schema, and a single bad pasted-content record is dropped instead of throwing away the whole history entry.\n\n**Details**\n\n- Validated fields: display text, pasted contents, timestamp, project, and an optional session ID.\n- Dropping a bad paste logs \"Dropping a malformed paste record from a history line\".\n- Load reporting now separates `history_load_parse_failed`, `history_load_shape_rejected` and `history_load_paste_record_dropped`, each with its own boolean field, alongside the existing `history_load_read_interrupted`.\n\n**Evidence**\n\n`history_load_shape_rejected`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}