{"version":"2.1.269","anchor":"auto-mode-classifier-skippedunrecognized-results-can-now-r","canonical_anchor":"auto-mode-classifier-skippedunrecognized-results-can-now-r","heading":"Auto-mode classifier: skipped\/unrecognized results can now retry instead of always blocking","tier":"internal","area":"Auto Mode","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/auto-mode-classifier-skippedunrecognized-results-can-now-r","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### Auto-mode classifier: skipped\/unrecognized results can now retry instead of always blocking\n\nAuto-mode classifier can now retry via a callback instead of always blocking on unavailable results\n\n**What**\n\nThe function that evaluates the safety classifier's results now accepts a callback. When the server's result was skipped or the classifier's response type isn't recognized, it now invokes that callback instead of automatically falling back to the \"blocking for safety\" response.\n\n**Why**\n\nPreviously, any skipped or unrecognized classifier result meant the action was blocked outright. Now there's a path to retry or handle that case differently, which can reduce unnecessary blocking when the classifier result is simply missing or malformed rather than genuinely unsafe.\n\n- Area: Auto Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}