Thursday, October 9, 2025
1 change · saas-18.3
Enhancements to existing features
The Peppol configuration screen now remains available even if the external service list cannot be loaded. This lets users continue important actions such as unregistering instead of being blocked by a temporary service error.
Original PR description
Handle `api/peppol/2/get_services` errors gracefully, without blocking critical section of peppol functionnal flow (deletion). If the API endpoint for services returns an error (which should not be affecting any users), the whole peppol config wizard is no longer accessible. The users will therefore not be able to unregister. Note that with this change, if we get an API error, all services will be marked as disabled (which is fair, and better than displaying an API request error) no-task Forward-Port-Of: odoo/odoo#228800