← Problem Library
Security L5 SECURITY-1572 · 8 min

A Turnstile verification secret rotates and one edge still uses the old key because the worker KV cache was never invalidated

The new secret is stored, but one worker still resolves the older secret from a stale KV entry.

SecurityPlatform ReliabilityLevel 5Pro8 min
Scenario

One edge still verifies Turnstile with the old secret after rotation.

What to check first
  • Identify the primary failure signal in the The New Stamp Was Delivered to the Booth and One Attendant Kept Pulling Yesterday's Seal From the Drawer Marked Temporary 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 KV invalidation 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.