{"version":"2.1.236","anchor":"transcript-tail-can-stop-collecting-at-an-api-error","canonical_anchor":"transcript-tail-can-stop-collecting-at-an-api-error","heading":"Transcript tail can stop collecting at an API error","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236\/e\/transcript-tail-can-stop-collecting-at-an-api-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.236","markdown":"### Transcript tail can stop collecting at an API error\n\nHistory collection can now stop at an API error so failed-request status is not replayed.\n\n**What**\n\nThe helper that gathers the recent slice of message history gained an option to stop as soon as it hits an API error message, returning an empty result if it had collected nothing yet. It is used to avoid replaying status after a failed request.\n\n**Evidence**\n\n`noStatusAfterApiError`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}