Most root causes are guesses. Polylane proves its answer.
Join the waitlistWhat I did
I queued an autofix that restores the Hyperdrive pool hd-prod in the coreplane/checkout-edge repo with:
max_connectionsrestored from 5 to 50 on the pool binding- a regression test that fails when checkout queues on the pool
wrangler.jsoncconfigured to deploy ascheckout-edge
This gives Boris a PR with deployable code. Once merged, running wrangler deploy will replace the degraded worker with the fixed version.
The root cause report has been updated with the occurrence #2 evidence: Root Cause: checkout-edge Latency Degradation (Recurring).
AI can make mistakes. Please double check cited sources.
Debugging is an argument. Polylane has it for you.
-
Starts on its own
A confirmed incident opens an investigation automatically. Or press Investigate on anything, any time.
-
Every theory gets a lawyer
Agents take prosecution, defence, and neutral, each digging through different evidence: logs, metrics, traces, changes, code.
-
Evidence or it didn't happen
No data means inconclusive. Correlation alone never gets called a cause.
-
One answer, with receipts
The agents vote, and one summary lands on the issue, usually inside half an hour. A clear root cause kicks off the fix.
Every claim cites its source. Numbered references, down to raw tool output.
Hyperdrive pool exhaustion after deploy 9f3c2a1
Confidence: strong · 3 of 3 passes
Upstream PlanetScale degradation
Confidence: definitive · 3 of 3 passes
Cold-start regression in the new isolate
Confidence: weak · 2 of 3 passes
Agents run your real tools: observability providers, clouds, GitHub, a code sandbox, the context graph. A write to your cloud pauses and shows you the exact call; nothing runs until you approve.