ProcessingHub Disconnected
Investigating - We have rolled back the previously deployed hotfix after discovering an issue that could cause processes to become stuck for a subset of customers. Our team is actively investigating the issue and working on a revised fix. We will provide another update as soon as we have more information. We apologize for the inconvenience and appreciate your patience. Previous incident: https://status.findock.com/incidents/fnl86pwphwf7
Aug 05, 2026 - 14:36 CEST

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
90 days ago
100.0 % uptime
Today
File processing (ProcessingHub) Operational
90 days ago
100.0 % uptime
Today
(Online) Payment API / Payment Service Providers Operational
90 days ago
100.0 % uptime
Today
Notifications from Payment Service Providers (WebHub) Operational
90 days ago
100.0 % uptime
Today
Giving pages Operational
90 days ago
100.0 % uptime
Today
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.

Aug 6, 2026

No incidents reported today.

Aug 5, 2026

ProcessingHub Disconnected
Resolved - Incident resolved. We have pushed out a hotfix that proactively rotates tokens to avoid token expirations. No action is required from customers after this change. We will continue to closely monitor app connections over the coming weeks.
Aug 5, 09:53 CEST
Identified - We have identified the root cause of unexpected ProcessingHub and WebHub disconnections. In scenarios where an access token does not expire (because the app connection is actively used), the refresh token remain unused over its 30-day lifespan. When the refresh token expires after 30 days, Salesforce revokes both the refresh token and the access token, causing the connections to ProcessingHub and/or WebHub to fail. For now, to prevent further disconnections, we are manually forcing access token renewals in cases where an unused refresh token is reaching its limit. A permanent solution is also in the works and will be rolled out next week.
Jul 31, 12:32 CEST
Investigating - Some customers have seen ProcessingHub being unexpectedly disconnected with a generic “expired access/refresh token” error from Salesforce. We are actively investigating the root cause. We have contacted customers directly whom we know have been impacted. We keep on monitoring all connection and reach out if it happens to your Salesforce environment. If you notice it is disconnected, you can reconnect from FinDock Setup > Connect. The initial sync with ProcessingHub may take some time for large data volumes. We sincerely apologize for the inconvenience.
Jul 27, 11:30 CEST

Aug 4, 2026

HOTFIX - Duplicate names, Bulk API 2.0 batch handling, and app token management
Completed - The scheduled maintenance has been completed.
Aug 4, 22:08 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Aug 4, 21:26 CEST
Scheduled - This hotfix bundles three important enhancements. First, we expand the deduplication logic API name collisions to properly catch and exclude null references in queries. Second, we fix an issue with very large payment schedule runs and Bulk API 2.0. The issue caused batch data loads to be missed, leaving the affected process unfinished, while moving to the next job, and ultimate causing, for instance, incorrect totals for counters related to the process and schedule. Thirdly, we implement scheduled access token renewals for FinDock’s connected apps. This ensures refresh tokens are used to renew access token so neither token expires. Prior to this hotfix, some orgs were being disconnected unexpectedly from WebHub and/or ProcessingHub because refresh tokens were not used within their 30-day lifespan. When a refresh token expires, Salesforce revokes both the refresh token and the access token.
Aug 4, 17:06 CEST

Aug 3, 2026

No incidents reported.

Aug 2, 2026

No incidents reported.

Aug 1, 2026

No incidents reported.

Jul 31, 2026

Jul 30, 2026

No incidents reported.

Jul 29, 2026

No incidents reported.

Jul 28, 2026

HOTFIX - Core, SEPA and ProcessingHub
Completed - The scheduled maintenance has been completed.
Jul 28, 22:17 CEST
In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary.
Jul 28, 21:39 CEST
Scheduled - This hotfix bundles the following enhancements: (1) Core update to re-add logic for handling API name collisions that was not available after the Summer '26 compatibility changes, (2) SEPA update to fix a user mode bug that prevented users with the correct permissions from using the Data Quality component, (3) ProcessingHub optimization to efficiently process very large numbers (millions) of deleted records, and (4) a workaround for ProcessingHub to parse Bulk API 2.0 error messages that can have broken formatting due to a known Salesforce issue.
Jul 28, 16:19 CEST

Jul 27, 2026

Jul 26, 2026

No incidents reported.

Jul 25, 2026

No incidents reported.

Jul 24, 2026

No incidents reported.

Jul 23, 2026

No incidents reported.

← Incident History Powered by Atlassian Statuspage