Get started Dashboard
Convex

Expert incident response for Convex

Our founding team picks up your incident, and Polylane's agents dig through your logs, metrics, traces and code with them.

  • Real engineers who've carried the pager The team has been on-call at Cloudflare, Webflow, Groq, Twilio, and Robinhood. They've been where you are right now.
  • Multi-cloud incident response Polylane investigates incidents across AWS, Cloudflare, Vercel, Kubernetes and the rest of your stack, from the edge to the database.
  • Unified context & investigation Logs, metrics, traces, deploys and code in one context graph. Connect in minutes, not weeks.
  • Least-privilege access New cloud accounts connect read-only, with scoped credentials. Nothing in production changes unless you allow it.

By submitting this form, you agree to our Privacy Policy.

My app on Convex is down. What should I do?

Check status.convex.dev first. If Convex reports nothing, open the Logs page for your production deployment in the dashboard, or run npx convex logs --prod: every query, mutation and action shows there with the error it threw. If the errors started with your latest push, redeploy the previous version of your functions, then fix forward.

  1. 1 Check Convex's status status.convex.dev lists incidents. If one matches what you see, the problem is upstream.
  2. 2 Read the function logs The dashboard's Logs page and npx convex logs --prod show each query, mutation and action with its error. Filter by the function that fails.
  3. 3 Line it up with your last deploy Compare the start of the errors with your latest npx convex deploy. A schema change can also fail a deploy when existing documents don't match it.
  4. 4 Check for limits Functions that read too much data or run too long fail with limit errors. The dashboard's Health page shows failure rates and the functions behind them.

How we resolve active incidents

  1. 1 Rapid onboarding A Polylane engineer reaches out, connects Polylane to your clouds, code and telemetry, and confirms what's affected.
  2. 2 Investigation & mitigation Polylane's agents investigate across logs, metrics, traces and recent changes, and an engineer works with you on the right mitigation.
  3. 3 Remediation, validation & monitoring The fix lands in your repo for your team to review. Polylane checks that things are back to normal and keeps watching every deploy after it.

Why teams choose Polylane

Every cloud in one graph AWS, Cloudflare, Vercel, Kubernetes and more, mapped into one context graph with your code.
Connected in minutes Connect with OAuth or the CLI. No agents to install, no code changes.
Real engineers on the other end Your report goes straight to the people who build Polylane.
Evidence for every claim Every finding links to the log line, metric or deploy behind it.
You stay in control Read-only by default. Nothing writes to production unless you allow it, and you can switch it off at any time.
Works with your coding agents Claude Code, Cursor and other agents reach Polylane over MCP, so they can dig in with you.
“polylane is so clean”
Sadok @yesadok

Common questions

Is Convex down or is it my app?

Check status.convex.dev. If it shows no incident, the Logs page shows which of your functions fail and why.

How do I see why a Convex function failed?

Open the Logs page in the dashboard or run npx convex logs --prod. Each failed call shows its error and the function it came from.

How do I roll back a Convex deployment?

Redeploy the previous version of your code with npx convex deploy, for example from the last good commit. Data written since stays in place.

Who will help me with a Convex incident?

Our founding team, engineers who have carried the pager for production systems at scale, working with Polylane's agents across your Convex deployments, code and telemetry.

Down on a specific platform?

Trusted by teams that ship to production every day