{"version":"2.1.260","anchor":"fixed-agent-empty-result-counting-for-workflow-agents","canonical_anchor":"fixed-agent-empty-result-counting-for-workflow-agents","heading":"Fixed agent_empty_result counting for workflow agents","tier":"notice","area":"Subagents","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260\/e\/fixed-agent-empty-result-counting-for-workflow-agents","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.260","markdown":"### Fixed agent_empty_result counting for workflow agents\n\nFixed a wrong empty-result count shown in the subagent usage summary.\n\nThe routine that builds the `<usage>` summary block for subagent\/workflow runs (`<agents_done>`, `<agents_error>`, `<agents_skipped>`, `<agents_empty_result>`) previously checked `resultPreview` against a stale outer-scope variable instead of the current loop item, which could produce a wrong empty-result count. It now checks `R.resultPreview` on the actual agent being iterated, fixing the `agents_empty_result` count reported in the usage summary.\n\n- Area: Subagents\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5"}