{"version":"2.1.307","anchor":"workflows-tool-reports-a-distinct-error-for-an-unsupported-r","canonical_anchor":"workflows-tool-reports-a-distinct-error-for-an-unsupported-r","heading":"Workflows give a clear error on an unsupported runtime","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/workflows-tool-reports-a-distinct-error-for-an-unsupported-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Workflows give a clear error on an unsupported runtime\n\nWhen workflows are off because the runtime is unsupported, Claude Code now says so with its own error instead of a general one\n\n**What**\n\nWhen the workflows feature is turned off because Claude Code is running on an unsupported runtime, the program environment it runs in, it now returns its own message for that case, with error code 17. Before, this case fell through to the general check for managed settings, the settings an organization enforces.\n\n**Why**\n\nIf you are on an unsupported runtime, you get the real reason workflows are unavailable instead of one that points at your organization's settings.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}