receptionist_connections_update_unconfirmed
Stripe did not answer the subscription-item update, so whether the connection change applied is unknown. The local count is unchanged; the signed customer.subscription.updated webhook reconciles it. Refresh billing shortly rather than assuming the change failed - the request is safely retryable because the target is absolute, never a delta, so setting N twice is setting N and no ambiguous outcome can double a fee. Also answered when Stripe returns a success the adapter cannot parse: a malformed 2xx is not a refusal, and Stripe may have applied the change before the parse failed. Since the prepaid month landed (ADR-0025 as amended 2026-08-18) the detail additionally states whether that month was already collected on this request, because "nothing changed" would otherwise be a lie about the customer's money; when it was, re-sending the same target completes the purchase and cannot charge a second month.
Problem shape
Every non-2xx response is an RFC 9457 application/problem+json body. The type URI below is stable and machine-matchable, so branch on the final path segment (the code) and treat the status as redundant confirmation. See the error-handling guide.
{
"type": "https://docs.vocapable.com/errors/receptionist_connections_update_unconfirmed",
"title": "…",
"status": 502,
"detail": "…",
"instance": "/v1/…"
}