Nobody should be on-call in 2026.
Agents that read your code, watch your infra, and fix production before you wake up.
· Early access currently rolling out.
Polylane finds issues in your app and fixes them for you, automatically.
It learns everything you run. Every cloud, every repo, every dependency: one live graph.
Topology
Search your cloud resources...
1,320 resources Galaxy Graph Table
cloudflare
checkout-edge Critical Critical to your architecture.
Issue hotspot: 4 issues in the last 7 days
Change hotspot: 12 changes in the last 7 days
coreplane · earth · Worker · Compute
cloudflare
hd-prod Critical Critical to your architecture.
Change hotspot: 7 changes in the last 7 days
coreplane · earth · Hyperdrive · Databases
AWS
ingest-events Standard Important to your architecture.
Issue hotspot: 2 issues in the last 7 days
coreplane-prod · us-east-1 · Lambda function · Compute
planetscale
payments-db Critical Critical to your architecture.
Issue hotspot: 1 issue in the last 7 days
Change hotspot: 3 changes in the last 7 days
coreplane · us-east · Database · Databases
It improves your observability. Missing logs, silent routes, swallowed errors: fixed before you need them.
Observability improvements for #218 polylane +22 −2
Requests do not produce one context-rich event
3 affected routes · found by the scan after the last sync
server/api/checkout.post.ts mirrors your existing OpenTelemetry setup; no new dependencies
export default defineEventHandler(async (event) => {
const body = await readBody(event);
- const order = await createOrder(body);
- return { orderId: order.id };
+ return tracer.startActiveSpan("checkout", async (span) => {
+ const canonical: Record<string, unknown> = {
+ route: "checkout",
+ requestId: event.context.requestId,
+ cartId: body.cartId,
+ traceId: span.spanContext().traceId,
+ };
+ try {
+ const order = await createOrder(body);
+ span.setAttributes({ "order.id": order.id, "order.amount_cents": order.amountCents });
+ Object.assign(canonical, { orderId: order.id, amountCents: order.amountCents, outcome: "ok" });
+ return { orderId: order.id };
+ } catch (err) {
+ span.recordException(err);
+ span.setStatus({ code: SpanStatusCode.ERROR });
+ canonical.outcome = "error";
+ throw err;
+ } finally {
+ span.end();
+ emitCanonicalLogLine(canonical);
+ }
+ });
});
Opened against the pull request's own branch, so it can merge before the branch does.
It stops risky changes before they hit prod. The incident that would have paged you dies before it merges.
github.com/coreplane/orders-api/pull/482
Add trigram index for order search #482
Open rvidal wants to merge 1 commit into
main from order-search-trgm Conversation 1 Commits 1 Checks 2 Files changed 1
polylane bot commented 2 minutes ago ···
Caution
Merging this pull request may degrade production (high impact).
Merging this blocks every write to orders while the index builds. migrations/0114_order_search_trgm.sql:3 adds CREATE INDEX … USING gin (search_text gin_trgm_ops) without CONCURRENTLY, and a plain CREATE INDEX takes a full write lock on orders for the whole build. Checkout sustains ~38 writes/s on that table; each one queues behind the lock until the build finishes.
To make this safe: build the index with CREATE INDEX CONCURRENTLY outside the transactional migration.
orders-db · writes per second · last 48h
projected lock window
02040
-48h -24h now
every one of these writes blocks while the index builds
Polylane analysed de91b47 for production impact.
Some checks were not successful 1 failing and 1 successful check
ci / test Successful in 2m 4s Details
Polylane production impact Non-concurrent index build locks writes on orders Details
Merging is blocked
It catches what slips through. Issues detected in minutes, before your users feel them.
Issues Critical latency degradation in checkout-edge worker Overview
Critical latency degradation in checkout-edge worker
Critical
Active
·Detected 3 hours ago
OverviewMetricsLogsTracesTimelineProperties
checkout-edge
Cloudflare Worker
View triggering check View incident
Critical latency degradation detected in checkout-edge worker: 18x+ P99 latency spikes sustained for 12 minutes
Request Duration
414 ms ▲ 43.1σ
Wall Time
416 ms ▲ 43.0σ
Request Duration
131 ms ▲ 2.6σ
Blast radius edge-gateway Cloudflare Worker ··· checkout-edge Cloudflare Worker ··· hd-prod Hyperdrive ··· payments-db PlanetScale ··· cart-svc Cloudflare Worker ···
Search your cloud resources...
5 resources Graph Table
edge-gateway Cloudflare Worker ··· checkout-edge Cloudflare Worker ··· hd-prod Hyperdrive ··· payments-db PlanetScale ··· cart-svc Cloudflare Worker ··· It investigates like it has something to prove. A proven root cause, receipts included.
Threads Critical latency degradation in checkout-edge worker Share
What 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).
Wall Time
checkout-edge worker · last hour
Wall Time P99
28,381ms
Wall Time P95
2,696ms
Wall Time P50
118ms
010k20k30k
18:0018:2519:00
Worked for 4m 12s
AI can make mistakes. Please double check cited sources.
Dig deeper...
Then it ends the incident. The permanent fix arrives: you review, it merges.
github.com/coreplane/payments-api/pull/491
Cap retries on the checkout webhook worker #491
polylane Open polylane wants to merge 1 commit into
main from polylane/autofix/chat/k3x9f2-4e7d21a Conversation 1 Commits 1 Checks 1 Files changed 2
polylane bot commented 6 minutes ago ···
Retries on the checkout webhook worker were unbounded: a failing delivery re-queued itself forever and amplified load on payments-api. This caps delivery at 5 attempts with exponential backoff and dead-letters the payload after the last one.
What changed
worker/deliver.ts gains MAX_DELIVERY_ATTEMPTS = 5 and backoff between attempts; exhausted payloads land in checkout-webhooks-dlq instead of re-queueing.
Validation
npm test — 214 passed. A forced failing delivery stopped after 5 attempts and appeared in the dead-letter queue.
Root cause · Why it's safe · Out of scope
polylane added commit 4e7d21a Verified
Review required At least 1 approving review is required
ci / test Successful in 3m 12s Details
Review required Waiting on your review: Polylane never merges on its own
Merging is blocked
Claude Code 
Codex 
OpenCode 
VS Code 
