FinDock incident

Stripe notification processing delays

Notice Resolved View vendor source →

FinDock experienced a notice incident on October 25, 2024 affecting Notifications from Payment Service Providers (WebHub), lasting 11d 22h. The incident has been resolved; the full update timeline is below.

Started
Oct 25, 2024, 10:27 AM UTC
Resolved
Nov 06, 2024, 08:34 AM UTC
Duration
11d 22h
Detected by Pingoru
Oct 25, 2024, 10:27 AM UTC

Affected components

Notifications from Payment Service Providers (WebHub)

Update timeline

  1. investigating Oct 25, 2024, 10:27 AM UTC

    Inbound reports for Stripe charge.succeeded and payment_intent.succeeded notifications may remain in Pending status instead of being processed as expected. This issue does not impact collection, but updates to payment data in Salesforce are delayed. We are actively investigating this issue. Until we have a resolution, we recommend checking for inbound reports with Pending status and either manually retrying Guided Matching on individual reports or using automation to set the Start Guided Matching checkbox to true on the Pending reports. The next update can be expected on Monday, October 28th, at the latest.

  2. investigating Oct 28, 2024, 01:54 PM UTC

    Although we haven't seen any new occurrences of this issue, we are still investigating it. A new update will be shared by Thursday, October 31st, at the latest.

  3. identified Oct 31, 2024, 07:02 PM UTC

    We have actively worked on this issue and developed several enhancements that are currently undergoing testing. Once all tests are successfully completed, we will deploy a patch for all customers using the Stripe for FinDock package. We will share an exact date and time for this deployment as soon as possible. If no other updates are shared beforehand, we will provide an update on Monday, November 4th.

  4. identified Nov 04, 2024, 03:18 PM UTC

    We will be deploying an update tonight containing several enhancements. All customers using the Stripe for FinDock package will receive this patch. We will continue to monitor the situation closely to ensure that the issue is resolved.

  5. monitoring Nov 05, 2024, 08:40 AM UTC

    A fix has been implemented and we are monitoring the results.

  6. resolved Nov 06, 2024, 08:34 AM UTC

    We haven't observed any new occurrences of this issue and will proceed to close the incident. We will continue to monitor the situation closely to ensure it remains resolved.