{"version":"2.1.220","anchor":"classifier-beta-rejection-latch-still-keys-off-a-null-placeh","canonical_anchor":"classifier-beta-rejection-latch-still-keys-off-a-null-placeh","heading":"Classifier beta-rejection latch still keys off a null placeholder","tier":"soon","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.220\/e\/classifier-beta-rejection-latch-still-keys-off-a-null-placeh","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.220","markdown":"### Classifier beta-rejection latch still keys off a null placeholder\n\nThe automatic retry that would drop a rejected classifier beta can never trigger in this build.\n\n**What**\n\nThe path that drops a classifier beta after an HTTP 400 followed by a successful bare retry is keyed on a beta constant that is `null` in both builds, so it never fires.\n\n**Details**\n\n- The latch bails out early when the constant is null, and the constant is declared as `null` in 2.1.219 and 2.1.220 alike.\n- The newly-sent auto-mode-classifier beta therefore has no automatic drop-on-400 path in this build.\n- The telemetry it would emit, `tengu_auto_mode_beta_latch` and `permission_auto_mode_classifier`, is present but unreachable.\n\n**Evidence**\n\n`tengu_auto_mode_beta_latch`\n\n- Area: Permissions\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Present in the build but not switched on"}