Skip to content

See it work

One issue, three artifacts, in the order they land in a Teams thread.

A payment capture times out against the gateway. Sentry raises the issue and webhooks it to the receiver, which verifies the signature and posts this card.

🔴 ERROR

STAGING · New Issue

PaymentIntentTimeout: Gateway did not acknowledge intent pi_3QwXm2Lk8Nv within 8s

Project
checkout
Issue
CHECKOUT-4B2
Culprit
checkout.services.payments in capture_intent
Open in Sentry

The gate lets this one through: it is error-level, staging is an investigated environment, and its release resolves to a commit SHA, so the session will read the code that actually produced the error rather than today’s default branch. The issue is queued with a debounce and picked up by the next sweep.

The session checks the repository out at that SHA, reads the traceback and the surrounding code, and posts its findings back. The receiver renders them as a reply in the alert’s own thread.

Automated investigation: CHECKOUT-4B2

Urgency: high · Confidence: high · Fixability: high · Intent: settled · Release: 79bad4b79fb0

submit_order wraps capture_intent in a bare except, so the gateway timeout is retried silently and the capture is reported as sent.

Next step: mirror refund_intent's explicit PaymentIntentTimeout branch in submit_order

Details

Intent settled by: refund_intent in src/checkout/services/payments.py raises PaymentIntentTimeout when the gateway times out, so a timed-out payment call is a failure, not a success; submit_order is the side that has not caught up

Evidence

- src/checkout/services/payments.py:184 in capture_intent the deadline branch raises but submit_order swallows it

Assumptions

- the 8s gateway ceiling is a product decision, not a bug

Open Details for the intent's source, the evidence, and the assumptions, which Teams collapses the same way.

The finding is that capture_intent raises on its polling deadline, but the caller wraps it in a bare except and reports the capture as sent, so the failure never surfaces. The suggested fix mirrors refund_intent, which already has an explicit timeout branch.

Urgency is high. A capture reported as sent when it was not puts payment data at risk, which would make this urgent in production, but the issue has only been seen in staging, so it is rated one level lower. Urgency says how much the issue matters and leads the status line so it is the first thing a reader scans.

Confidence is high, fixability is high, and intent is settled: the right behavior for a timed-out capture is not in question, because refund_intent in the same module already treats the timeout as a failure, and the fix only brings submit_order in line with it. The finding names that source, and the card shows it under Details. Those three values decide whether the session goes on to attempt a fix; urgency plays no part in that decision.

With autofix.enabled on, a finding at high confidence and high fixability, with its intent settled, clears the gate, so the receiver answers the findings POST with a grant. The same session then judges drift against the base branch, re-verifies the root cause, writes the change and a test for it, and sends the changed files back to the receiver with the base commit and the pull request text. The receiver opens the pull request as the App and reports the outcome into the same thread.

Nothing merges automatically. The session has no way to write to GitHub; the receiver mints a token that can write contents and open pull requests in one repository for one hour and nothing else, spends it, and the pull request waits for a human exactly like any other.

The renderer handles four severities. Fatal, error, and warning are investigated. Info is posted for visibility and says so, unless it is an N+1 performance issue, which is investigated like an error.

💥 FATAL

STAGING · New Issue

PaymentIntentTimeout: Gateway did not acknowledge intent pi_3QwXm2Lk8Nv within 8s

Project
checkout
Issue
CHECKOUT-4B2
Culprit
checkout.services.payments in capture_intent
Open in Sentry

🟠 WARNING

STAGING · New Issue

PaymentIntentTimeout: Gateway did not acknowledge intent pi_3QwXm2Lk8Nv within 8s

Project
checkout
Issue
CHECKOUT-4B2
Culprit
checkout.services.payments in capture_intent
Open in Sentry

🔵 INFO

STAGING · New Issue

PaymentIntentTimeout: Gateway did not acknowledge intent pi_3QwXm2Lk8Nv within 8s

Project
checkout
Issue
CHECKOUT-4B2
Culprit
checkout.services.payments in capture_intent

ℹ️ This kind of issue is not auto-investigated.

Open in Sentry