Is FinDock down?

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 ([email protected]) 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 [email protected] if you have any questions.

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.

Salesforce is currently experiencing an incident (https://status.salesforce.com/incidents/20004433). Because FinDock runs natively on the Salesforce platform, this may affect some FinDock features while the incident is ongoing. What this could mean for you: - Donation/payment pages may be temporarily inaccessible, or fail to successfully initiate a payment - Notifications may be delayed - Payment processing within Salesforce may be affected The full impact is still unclear, but it's most likely that this Salesforce incident means payments cannot be processed within Salesforce now. What we're doing: FinDock will automatically retry notifications where possible once the underlying Salesforce issue is resolved. We're closely monitoring the incident and will act as soon as Salesforce's systems are back to normal. What you can do: Please keep an eye on Salesforce's status page (https://status.salesforce.com/incidents/20004433) for the latest updates on the underlying incident.

FinDock will automatically retry notifications where possible once the underlying Salesforce issue is resolved. We're closely monitoring the incident and will act as soon as Salesforce's systems are back to normal.

Salesforce Rollout in Progress — Services Recovering Salesforce has confirmed they are rolling out a fix for the earlier incident (status.salesforce.com/incidents/20004433). The rollout is progressing region by region, and services are returning to normal in regions where it has completed. Salesforce continues to monitor the rollout and is working on a permanent fix. This also means FinDock is fully operational again. What FinDock is doing: Notifications affected during the incident have been resent, or are in the process of being resent. We will close this incident but will continue monitoring the situation closely as Salesforce completes the rollout, and will provide a further update if anything changes.

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

This incident has been resolved.