All Systems Operational

About This Site

Here you can find the actual status of our services. If there are any incidents known to us they will be posted and updated here. You can also find when we perform Maintenance to any of our systems. Subscribe to be notified of new Incidents, Maintenance and next releases. Have a look at https://docs.findock.com/release-notes for a full overview of our upcoming releases.

- For the status of your specific Salesforce instance, please visit https://status.salesforce.com/.
- For the status of Heroku, please visit https://status.heroku.com/.

If you wish to report an incident, please visit https://findock.com/support

Uptime over the past 90 days. View historical uptime.
FinDock Core & Source packages Operational
File processing (ProcessingHub) Operational
(Online) Payment API / Payment Service Providers Operational
Notifications from Payment Service Providers (WebHub) Operational
Giving pages Operational
Sandboxes Operational
FinDock Knowledge Base Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

OCT 25, 2026 | Sandbox Release - November '26 Oct 25, 2026 20:00-21:00 CET

The FinDock November '26 release will be pushed to Sandboxes. During this event features will be available with no disruptions in services. The release notes will be published on docs.findock.com the Wednesday before the Sandbox release.
Posted on Oct 20, 2026 - 10:50 CEST

Nov 22, 2026 | Production Release - November '26 Nov 22, 2026 20:00-21:00 CET

The FinDock November '26 release will be pushed to Production. During this event features will be available with no disruptions in services. The release notes will be available on docs.findock.com the Wednesday before the Sandbox release.
Posted on Oct 20, 2026 - 10:52 CEST

Oct 20, 2026

No incidents reported today.

Oct 19, 2026

HOTFIX - Authorize.net and Swish payment schedules
Completed - The scheduled maintenance has been completed.
Oct 19, 16:26 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Oct 19, 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.
Oct 19, 15:25 CEST

Oct 18, 2026

No incidents reported.

Oct 17, 2026

No incidents reported.

Oct 16, 2026

No incidents reported.

Oct 15, 2026

No incidents reported.

Oct 14, 2026

No incidents reported.

Oct 13, 2026

No incidents reported.

Oct 12, 2026

No incidents reported.

Oct 11, 2026

No incidents reported.

Oct 10, 2026

No incidents reported.

Oct 9, 2026

No incidents reported.

Oct 8, 2026

WebHub and ProcessingHub Disconnections Following Salesforce incident
Resolved - We have confirmed with SFDC support that this was related to the Salesforce incident. Impacted customers have been contacted and issues were resolved. We have had no new occurrences, so no further action is required and we are closing the incident.
Oct 8, 12:07 CEST
Identified - Following the recent Salesforce incident (status.salesforce.com/incidents/20004433), we've identified that some orgs experienced a disconnection of their WebHub Notification Gateway and/or ProcessingHub connections. This is most likely related to the Salesforce incident, though we are still investigating the detailed root cause. We are working on proactively reaching out to customers who may be impacted.

How to check if you are affected:
Go to FinDock Setup > Click Connect > Click Webhub tab and verify if there is an error
Go to FinDock Setup -> Click Connect -> Click ProcessingHub and verify if there is an error
What you need to do when you are affected:
Please reach out to FinDock support (support@findock.com) so we can verify the status of the connection/processes and suggest next steps.

What is the impact:
PSP notifications can be resent and reprocessed once WebHub is reconnected, so no data is permanently lost. However, donation/payment pages relying on this connection would not have been able to initiate payments during the disconnected period.
Processes running on ProcessingHub can be unblocked or retried by us once the connection is restored.
Please reach out to support@findock.com if you have any questions.
Sep 17, 12:10 CEST
PayLinks Due Date and ProcessingHub update config error
Completed - The scheduled maintenance has been completed.
Oct 8, 12:05 CEST
Scheduled - This hotfix resolves two issues. One caused the Due Date on PayLinks payment forms to appear blank. This is now fixed so that Due Date appears as expected. The second fix resolves an issue where processes fail the "Update Config data if outdated" step. The issue was caused by a conflict between the scheduled token renewal logic introduced in the September ‘26 release and existing auto-retry logic on ProcessingHub. We've updated the auto-retry logic so that 403 errors from the Salesforce Identity URL don't block retries.
Oct 8, 12:05 CEST

Oct 7, 2026

No incidents reported.

Oct 6, 2026

No incidents reported.

Incident History Powered by Atlassian Statuspage