{"version":"2.1.233","anchor":"eval-suites-stop-at-the-first-authentication-failure","canonical_anchor":"eval-suites-stop-at-the-first-authentication-failure","heading":"Eval suites stop at the first authentication failure","tier":"notice","area":"Plugins","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233\/e\/eval-suites-stop-at-the-first-authentication-failure","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.233","markdown":"### Eval suites stop at the first authentication failure\n\nAn eval suite stops immediately when the first run is rejected for bad credentials.\n\n**What**\n\nIf the very first run in an eval suite is rejected for bad credentials, the suite halts immediately rather than working through every remaining case and failing each one the same way.\n\n**Details**\n\n- The stop is reported as `auth_failed`, with a new `auth_preflight_failed` alongside it; previously partial runs were always attributed to `cost_ceiling`.\n- The printed message points you at the credential error above and asks you to re-run.\n\n**Evidence**\n\n`every remaining run would fail the same way, so the suite stops here. Fix the credential above and re-run.`\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}