One hostname still bypasses inspection after WAF exception cleanup.
A WAF exception is removed and one host still bypasses inspection because the zone ruleset keeps the retired skip action in phase cache
The active config is correct, but one phase cache still restores the previous skip action on a single hostname.
Scenario
What to check first
- Identify the primary failure signal in the The Blanket Pass Was Revoked and One Side Desk Still Pulled the old approval card from the folder tucked under the counter 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 phase cache before editing the ruleset 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