{"version":"2.1.271","anchor":"teleport-relay-refuses-to-arm-if-the-transcript-already-show","canonical_anchor":"teleport-relay-refuses-to-arm-if-the-transcript-already-show","heading":"Teleport relay refuses to arm if the transcript already shows a whole-history end marker","tier":"internal","area":"Internals","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/teleport-relay-refuses-to-arm-if-the-transcript-already-show","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Teleport relay refuses to arm if the transcript already shows a whole-history end marker\n\nA server-side session relay now refuses to start if the transcript is already marked complete\n\n**What**\n\nBefore a server-driven 'teleport relay' (a mechanism for continuing a session on the server) arms itself, it now checks the lines after its starting point for a marker that indicates the whole conversation history has already ended. If that marker is present, it refuses to arm and reports a new `relay_already_ended` error instead of proceeding as if there were more to relay.\n\n**Why**\n\nThis prevents the relay from starting up on a transcript that's already finished, avoiding wasted or incorrect work on a conversation that has nothing left to continue.\n\n- Area: Internals\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}