← Problem Library
Security L5 SECURITY-1602 · 8 min

A Turnstile secret rotation is complete and one page still rejects humans because the worker KV binding keeps the old site secret

The token pair is rotated, but one worker binding still reads a stale secret from KV.

SecurityPlatform ReliabilityLevel 5Pro8 min
Scenario

One page still rejects humans after Turnstile secret rotation.

What to check first
  • Identify the primary failure signal in the The New lock code was given to the concierge and One side door still checked visitors against the slip left in the drawer from last week scenario.
  • Separate visible symptoms from the underlying technical dependency.
  • Describe the safest recovery path and the follow-up prevention work.
Checking checklist
  1. Summarize the current impact and the last known change.
  2. Collect direct evidence from logs, runtime state, and configuration before changing anything.
  3. Separate immediate recovery from permanent prevention work.
Recovery and prevention

Inspect edge bindings before rotating again.

Questions worth viewing together
Should I translate commands, logs, or product names?

No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.

What should the answer focus on?

State the root cause, the evidence that supports it, and the safest recovery direction.

Why can the scenario remain in the original language?

The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.