{"version":"2.1.246","anchor":"error-results-and-stream-events-echo-the-originating-prompt-","canonical_anchor":"error-results-and-stream-events-echo-the-originating-prompt-","heading":"Error results and stream events echo the originating prompt id","tier":"use","area":"SDK","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246\/e\/error-results-and-stream-events-echo-the-originating-prompt-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.246","markdown":"### Error results and stream events echo the originating prompt id\n\nErrors and stream events now echo the prompt id that started the turn.\n\n**What**\n\nThe error result message and the first non-ping stream event of a turn can both carry `user_message_uuid`, the client uuid of the prompt that started the turn, so a stream or a failure can be matched to its send immediately.\n\n**Details**\n\n- The schema field is optional, so older producers simply omit it.\n- Absent on meta and scheduled turns and on any turn submitted without a client uuid.\n\n**Evidence**\n\n`Client uuid of the user message that triggered this turn (submitMessage options.uuid), stamped on the turn's FIRST non-ping stream event only`\n\n- Area: SDK\n- Names: `user_message_uuid`\n- Tier: Use it now\n- Useful: 2\/5\n- Signal: 2\/5"}