One worker still verifies with the old Turnstile key after rotation.
A Turnstile secret rotates and one worker still verifies with the old key because a durable object holds the stale binding
The account secret is current, but one worker path still resolves verification through a durable object binding from before rotation.
Scenario
What to check first
- Identify the primary failure signal in the The New Seal Was Delivered to the Counter and One attendant kept using the stamp locked in the side 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
- Summarize the current impact and the last known change.
- Collect direct evidence from logs, runtime state, and configuration before changing anything.
- Separate immediate recovery from permanent prevention work.
Recovery and prevention
Inspect durable bindings before rotating the secret again.
Questions worth viewing together
No. Keep commands, logs, file names, APIs, and product names unchanged, then explain the reasoning in the selected UI language.
State the root cause, the evidence that supports it, and the safest recovery direction.
The source scenario is treated as an incident artifact. Guidance, checklist, hints, and explanations can be localized around it.
Similar cases seen in the field