Scheduled maintenance is currently in progress. We will provide updates as necessary.
Posted Oct 19, 2026 - 15:26 CEST
Scheduled
This hotfix resolves two issues with payment schedule runs for Authorize.net, one issue for Swish payment schedules. The first Authorize.net issue could lead to the status of processed installments to remain New. The issue is caused by race conditions between payment schedule processing jobs and the timing of inbound notifications. To counter these race conditions, we have added new processing checks and additional logic around status locking and updating. In addition, we added new, more transparent error handling to better surface errors that may arise from race conditions. The second issue could occur with large payment schedule runs, where installments may fail with a timeout error related to a Salesforce callout time limit. To reduce the risk of this issue occurring, we have improved the queueable framework for Authorize.net payment schedules with optimized job sizes, better debouncing, and more transparent logging to better support reconciliation of installments that fail due technical errors. For Swish, this hotfix resolves a race condition with Swish installments collected through payment schedules. In some scenarios, collected installments appear to be stuck with Pending processing status. The issue can arise when the paid notification arrives before the payment schedule has finished. We have introduced new measures to help ensure this race condition is avoided and prevent closed states like Collected from getting changed back to Pending processing.
Posted Oct 19, 2026 - 15:25 CEST
This scheduled maintenance affected: (Online) Payment API / Payment Service Providers and Notifications from Payment Service Providers (WebHub).