{"version":"2.1.259","anchor":"per-scope-row-cap-added-to-the-agent-orchestration-world-e","canonical_anchor":"per-scope-row-cap-added-to-the-agent-orchestration-world-e","heading":"Per-scope row cap added to the agent-orchestration \"world\" engine","tier":"internal","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/per-scope-row-cap-added-to-the-agent-orchestration-world-e","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Per-scope row cap added to the agent-orchestration \"world\" engine\n\nThe workflow fact engine now caps rows per scope, emitting a runaway event and retracting the scope when it is exceeded.\n\nThe internal fact\/rule engine backing `agent()` \/ `parallel()` \/ `pipeline()` workflows now tracks how many rows accumulate under each scope. If a scope exceeds a per-scope cap, it emits a 'runaway' event and automatically retracts that scope, rather than relying solely on the existing global `maxRows` cap.\n\n- Area: Workflows\n- Names: `maxRows`\n- Tier: Under the hood\n- Useful: 3\/5\n- Signal: 3\/5"}