# xCloud v2.9.12.1

> Released November 11, 2026

**Release Mode and Payment Fixes**

Changing environment variables on a Node.js site now works again after you turn Release mode off. Release mode no longer asks you to remove a pull script you never wrote. When a payment is declined, xCloud now tries your other saved cards before it emails you.

## 🐞 Bug Fixes

-   **Release Mode**
    -   On a Node.js site where you turned Release mode off, clicking **Update Environment** now restarts the app with the new values. Before, the save said "Env Updated" but visitors got 502 errors until the next deploy. [Zero-Downtime Deployments for Node.js Apps in xCloud](/docs/zero-downtime-deploys-for-node-js-apps/)
    -   Release mode no longer refuses a site whose **Git Pull Script** is an older copy of xCloud's own default. Before, it said "This site has a custom pull script" and asked you to remove it. A script you edited yourself is still refused. [Release Mode Messages and Fixes in xCloud](/docs/release-mode-messages-and-fixes/)
-   **Billing**
    -   When an automatic payment for a new invoice is declined, xCloud now tries your team's other saved cards. Before, only the default card was tried.
    -   You now get one failed-payment email, after every saved card has declined. Before, you got one for each declined card, even when a later card paid.
-   **AI Assistant**
    -   The chat no longer leaves "Update failed" in place when a WordPress update finishes late and succeeds. It now posts a correction.

## Please note

-   If you turned Release mode off on a Node.js site before this release, deploy the site once. After that, environment changes apply as expected.
