Monday, April 20, 2026
1 change · saas-19.2
Resolved issues and error corrections
If the connection drops while waiting for a Viva.com payment confirmation, the POS now keeps checking instead of stopping too early. This reduces the risk of a customer being charged on Viva.com without the payment being confirmed in the point of sale, while also showing a one-time warning that connectivity was lost.
Original PR description
When a payment was sent to Viva.com and the connection dropped before receiving confirmation, the polling loop in waitForPaymentConfirmation would stop because _handleOdooConnectionFailure set the payment status to "retry" and rejected the promise. This left the payment debited on Viva's side but unconfirmed in the POS. Now the polling uses a direct silent ORM call instead of _call_viva_com to avoid triggering _handleOdooConnectionFailure. On connection failure, the poll silently retries on the next interval until a definitive success/failure response is received. A one-time warning notification informs the user that connectivity was lost. --- I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr Forward-Port-Of: odoo/odoo#259564