Worker Failure Trace Correlator
Group supplied Worker events by trace. Correlate a generic Fetch failed only when earlier evidence exists; leave the rest honestly unresolved.
Replace one terminal string with its trace.
Load the bundled evidence or paste a normalized export. Missing upstream telemetry remains a visible gap rather than a guessed diagnosis.
—
—
—
Why one trace resolves and another does not.
The rules use explicit same-trace evidence. Product anecdotes and a high memory percentage never substitute for an event.
Memory pressure
A generic fetch is correlated to memory only when an explicit OOM event appears earlier in the same trace. The user ceiling adds context but cannot trigger the classification.
KV rate limit or Workers AI upstream
A preceding 429/rate-limit event supports kv_rate_limit. Explicit model or inference unavailability supports workers_ai_upstream. Neither rule claims current product status.
model unavailable → Fetch failed = workers_ai_upstream
Unresolved generic failure
If Fetch failed has no earlier explicit event in its trace, the correct result is unresolved_fetch. The missing evidence is itself the actionable finding.
Limitations
This is correlation over supplied evidence, not proof of platform root cause. It does not fetch live logs, status, configuration, billing, cache state, or model availability.