{"version":"2.1.304","anchor":"workflow-compile-errors-distinguish-slash-mismatch","canonical_anchor":"workflow-compile-errors-distinguish-slash-mismatch","heading":"Workflow compile failures are reported with a separate reason for one kind of error","tier":"internal","area":"Workflows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/workflow-compile-errors-distinguish-slash-mismatch","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Workflow compile failures are reported with a separate reason for one kind of error\n\nWhen a workflow fails to compile because of one particular kind of error, Claude Code now reports a separate reason instead of a general syntax error\n\n**What**\n\nWhen a workflow fails to compile, Claude Code records the failure in its usage data. Failures caused by one particular kind of error are now recorded as a slash mismatch. Every other compile failure is still recorded as a syntax error, as all of them were before.\n\n**Why**\n\nThis only changes what Claude Code reports about the failure. What you see when a workflow fails to compile is not affected.\n\n- Area: Workflows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}