After extensive monitoring, we are now marking this incident as resolved.
Unfortunately, our investigations revealed that we missed some Zap trigger events during the incident, and we cannot recover this data. We're in the process of directly reaching out to customers who experienced data loss during this incident. Please keep an eye on your inbox for further information.
Our team has replayed the Zap Runs with a “Playing” status in Zap History due to this incident. If you happen to come across any other Zap Runs with a “Playing” status, feel free to replay them following this guidance:
Our engineers have identified areas where failed / Held Zap runs occurred during this incident and we have continued to replay them in batches. If you see held Zap runs or Zap runs that are still stuck in 'Playing' mode in your Zap History that you expected to run by now, you can attempt to replay those safely with no conflict to our team's work to resolve failed tasks.
If still seeing issues with past Zap runs, the team is working to recover these so they can be successfully played. If any data loss is detected after our remaining recovery efforts, we'll be transparent in reporting that to our users.
You can expect new Zap runs to be running regularly without any impact going forward.