{"version":"2.1.228","anchor":"resuming-an-agent-transcript-says-why-it-could-not-be-loaded","canonical_anchor":"resuming-an-agent-transcript-says-why-it-could-not-be-loaded","heading":"Resuming an agent transcript says why it could not be loaded","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/resuming-an-agent-transcript-says-why-it-could-not-be-loaded","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Resuming an agent transcript says why it could not be loaded\n\nLogs now say why a subagent transcript could not be resumed instead of just \"not found\".\n\n**What**\n\nWhen a sub-agent transcript cannot be resumed, the logs now distinguish a missing transcript, one the storage layer refused for permission reasons, and an outright error, instead of a bare \"not found\".\n\n**Details**\n\n- Results are also tagged with how they were served, so a cached load can be told apart from a fresh one.\n\n**Evidence**\n\n`getAgentTranscript: the storage backend cannot serve this agent transcript (permission); not resumable`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}