Start with the alert.
Get a cause you can check.
Infrastructure, telemetry and code agents work in parallel and share what they find. Your engineers get the evidence, the open questions and a proposed fix without running every search themselves.
How Ace investigates an incident
Orders stalled after a schema change
A migration waits on a lock held by reporting
Infrastructure agentOrder delivery waits behind the same session
Telemetry agentThe migration runner retries without a timeout
Code agentawait db.transaction(async (tx) => {+ await tx.sql`SET LOCAL lock_timeout = '2s'`; await applyMigration(tx, migration);− retry: untilSuccess()+ retry: boundedBackoff({ attempts: 3 })In production with
Understand the fix
before you approve it.
Trace the patch back to the failure it addresses. Review the target, the tests and the recovery checks before a change reaches production.
Bound migration locks and retries #843
Openace wants to merge 2 commits into main
await db.transaction(async (tx) => {+ await tx.sql`SET LOCAL lock_timeout = '2s'`; await applyMigration(tx, migration);});− retry: untilSuccess()+ retry: boundedBackoff({ attempts: 3 })Fix pull request
A minimal code or infrastructure-as-code repair, tested in an isolated sandbox, reviewed for correctness, data safety and operations, and opened for review.
Revert or roll back
An exact revert pull request, or a known-healthy revision redeployed through a workflow your administrator has confirmed.
Kubernetes changes
Restart, scale or patch workloads in the namespaces you grant, under the same approvals.
Deploys, jobs and flags
Roll back a Vercel deployment, replay failed Trigger.dev runs, stage a PostHog flag rollout or open a PlanetScale deploy request.
Before you connect Ace.
Give your engineers
their time back.
Watch Ace investigate an incident, prepare the fix
and verify that service recovered.