EverTrue incident

EverTrue/Scheduled Exports - Failed Delivery of Scheduled Exports 11/23-11/25

Minor Resolved View vendor source →

EverTrue experienced a minor incident on November 25, 2024 affecting Exports, lasting 1d 10h. The incident has been resolved; the full update timeline is below.

Started
Nov 25, 2024, 01:41 PM UTC
Resolved
Nov 27, 2024, 12:30 AM UTC
Duration
1d 10h
Detected by Pingoru
Nov 25, 2024, 01:41 PM UTC

Affected components

Exports

Update timeline

  1. investigating Nov 25, 2024, 01:41 PM UTC

    We are currently investigating an issue which prevented some scheduled EverTrue exports from being delivered at the expected time starting 11/23. We apologize for the issue and are working to resolve as quickly as possible. We ask that you please do not attempt to manually run the exports while we work through the issue. If you have any questions, please reach out to [email protected]

  2. identified Nov 25, 2024, 03:20 PM UTC

    We have identified the issue and are issuing a fix now. Failed exports will begin being delivered to affected accounts' SFTP exports folders shortly. We apologize for the inconvenience, if you have any questions please reach out to [email protected]

  3. monitoring Nov 25, 2024, 05:05 PM UTC

    A fix has been implemented and we are monitoring the results. Failed export files are being generated and delivered, and we appreciate your patience as we work through the backlog. If you have not received your failed export by end of day, please reach out to [email protected].

  4. identified Nov 26, 2024, 01:17 PM UTC

    Our team has identified an additional issue which prevented some missing exports from being created/delivered as expected. We apologize for the issue and are working to resolve this as quickly as possible. If you have any questions, please reach out to [email protected]

  5. monitoring Nov 26, 2024, 05:59 PM UTC

    A new fix has been implemented and we are monitoring the results. Please reach out to [email protected] if you have any questions.

  6. resolved Nov 27, 2024, 12:30 AM UTC

    This incident has been resolved. If you have any questions, please reach out to [email protected].