{"version":"2.1.242","anchor":"result-output-documents-its-pending-user-turn-count","canonical_anchor":"result-output-documents-its-pending-user-turn-count","heading":"Result output documents its pending-user-turn count","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/result-output-documents-its-pending-user-turn-count","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Result output documents its pending-user-turn count\n\nThe result message documents exactly which queued sends its pending count includes.\n\n**What**\n\nThe result message field counting queued sends now explains itself: it counts only your own sends still waiting when the result was produced, queued sends may merge together, entries the system queued are not counted, and the field is missing on results from a fatal startup failure.\n\n**Evidence**\n\n`User-initiated sends still waiting in the command queue when this result was produced.`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}