stripe_livemode_detected
Stripe answered a call in live mode (livemode: true anywhere in the answer).
HTTP 502 · api_error · not retryable
What happened
Section titled “What happened”Stripe answered a call in live mode (livemode: true anywhere in the answer). The breaker disabled the Stripe connector at once: no further request leaves, the connector’s health reason is livemode_detected, the admin deed connector.disabled is sealed with Stripe’s request id, and an alert goes to the server log. The action is recorded as unknown and its deed is UNVERIFIABLE, because something may have happened in live mode. The agent sees only that the connector is disabled.
What to do
Section titled “What to do”Find the request id from the deed (connector.disabled) in your Stripe dashboard and check what it did. Replace the key with a sandbox key, then set the connector back to active in Console › Connectors and run deedglass connector test stripe.
Example
Section titled “Example”{ "error": { "type": "api_error", "code": "stripe_livemode_detected", "message": "The stripe connector is disabled. An admin has been alerted.", "param": null, "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d", "doc_url": "https://docs.deedglass.com/errors/stripe_livemode_detected" }}The message is for a person and can get more exact over time: branch on type and code, never on the message.
In the SDKs
Section titled “In the SDKs”| SDK | Raised as |
|---|---|
TypeScript (@deedglass/sdk) |
APIError with code === "stripe_livemode_detected" |
Python (deedglass) |
deedglass.APIError with .code == "stripe_livemode_detected" |