Databases
PostgreSQL, MySQL and MongoDB, with read-only credentials. TraceX learns your schema and how tables link, and runs read-only queries only.
TraceX connects to the systems where your data, code and signals live, with read-only access you can revoke at any time.
PostgreSQL, MySQL and MongoDB, through read-only credentials. TraceX writes the query, runs it, and keeps only what it found.
SELECT id, order_id, state, created_atFROM refundsWHERE state = 'pending' AND created_at > '2026-10-21'
| id | order_id | state | created_at |
|---|---|---|---|
| rf_9921 | 48213 | pending | Oct 21 09:12 |
| rf_9934 | 48190 | pending | Oct 21 11:40 |
| rf_9958 | 48236 | pending | Oct 22 08:03 |
| rf_9987 | 48271 | pending | Oct 23 16:55 |
| … 30 more rows | |||
34 refunds are stuck in pending, every one created after Oct 21.
Code, commits and deploys through the GitHub App. TraceX finds the change that caused it and opens the fix as a pull request.
Opened by TraceX from the investigation · 1 file changed
The migration renamed the state; refunds.py still filters on the old one.
Issues and stack traces, matched to the deploy that started them.
chargeCard · first seen Oct 22, 14:02
node_modules/stripe/lib/charges.jscreatesrc/checkout/payment.ts:88chargeCardsrc/checkout/submit.ts:41onSubmitIt started with deploy a1c9e2: on a retry the payment intent is undefined.
TraceX searches the logs at the time of the issue and picks out the lines that explain it.
Each card error retried the charge without an idempotency key, so 6 orders were charged twice.
TraceX writes the Logs Insights query, runs it, and reads the events.
fields @timestamp, @message| filter @logStream like /refund-worker/| sort @timestamp desc
The worker runs every minute and finds nothing: its filter no longer matches any refund.
Each new customer email starts an investigation, and ends with a reply ready to send.
Refund still not received · My refund from last week still hasn't arrived. Order #48213.
Mention TraceX in a thread and get the answer, with its evidence, right there.
@TraceX why was order 48190 charged twice?
A card error retried the charge without an idempotency key, so the second attempt charged again 1. 6 orders were hit on Oct 22 2.
TraceX picks up the ticket, comments the root cause and links the fix.
Reported by 3 customers · Priority high
Safari blocks the cookie the 3-D Secure frame needs, so the challenge never loads and checkout waits until it times out 1.
Linked pull request
PostgreSQL, MySQL and MongoDB, with read-only credentials. TraceX learns your schema and how tables link, and runs read-only queries only.
GitHub, through the TraceX GitHub App: code search, files, recent commits and deploys, pull requests and reviews.
Sentry issues and stack traces, Datadog and CloudWatch logs, correlated with the time of the issue.
A Gmail support inbox, Slack and Jira: TraceX starts investigations and answers questions where your team works.
Claude through Anthropic or AWS Bedrock, Gemini, and open-weight models on Bedrock, with automatic fallback.
Use your own Anthropic or Gemini API key, so AI usage is billed to your account, never through TraceX.
TraceX is free during the private beta. Connect a database and a repository and ask your first question in minutes.