{"version":"2.1.242","anchor":"result-messages-report-how-many-of-your-sends-are-still-queu","canonical_anchor":"result-messages-report-how-many-of-your-sends-are-still-queu","heading":"Result messages report how many of your sends are still queued","tier":"notice","area":"Agents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/result-messages-report-how-many-of-your-sends-are-still-queu","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Result messages report how many of your sends are still queued\n\nResult messages now report how many of your sends were still queued.\n\n**What**\n\nSDK and stream-JSON result messages now carry an optional integer `queued_turn_count`, the number of sends you initiated that were still waiting in the command queue when the result was produced. It is live on this build, not gated.\n\n**Details**\n\n- The field is optional in both result schemas and is populated on the result message itself.\n- One helper zeroes it under a single condition, so a reported zero is not always a literal empty queue.\n- The name does not appear in the previous bundle.\n\n**Evidence**\n\n`queued_turn_count`\n\n- Area: Agents\n- Names: `queued_turn_count`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}