{"version":"2.1.271","anchor":"workflow-runs-now-track-rate-limit-waits-in-the-journal","canonical_anchor":"workflow-runs-now-track-rate-limit-waits-in-the-journal","heading":"Workflow runs now track rate-limit waits in the journal","tier":"internal","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271\/e\/workflow-runs-now-track-rate-limit-waits-in-the-journal","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.271","markdown":"### Workflow runs now track rate-limit waits in the journal\n\nWorkflow runs now record rate-limit waits in the task journal\n\n**What**\n\nWhen Claude Code runs a workflow (a script that orchestrates multiple agents), it now tracks moments when execution has to pause because of a rate limit. A new `onRateLimitWait` callback is wired into both the path where a sub-agent runs a workflow and the path where a workflow runs directly, recording these waits in the task registry.\n\n**Why**\n\nThis gives better visibility into why a workflow run is taking longer than expected, since rate-limit waits are now tracked rather than being an invisible pause.\n\n- Area: Workflows\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}