Our engineers have been monitoring the implemented fix, and our monitoring shows this incident to be resolved!
From 13:30 UTC (06:30 PT) to 17:30 UTC (10:30 PT) today, we began experiencing lag in Zap Runs and tasks showing up in Zap History. We discovered an issue with a failed search node that could not store data. Once identified, we worked to implement a fix for the issue.
All task processing continued to function as expected, and no data was lost. This incident only impacted Zap Runs and tasks from appearing in Zap History.
At this time, Zap Runs and tasks should appear in your Zap History as expected. No action is needed from any Zapier customers.
We sincerely appreciate your patience while we resolved the issue. Please reach out to our Support Team if you need help or are experiencing other issues: https://zapier.com/app/get-help
Posted Jun 21, 2022 - 14:55 PDT
Monitoring
A fix has been implemented, and Zap History is no longer behind. We are monitoring the results at this time.
Posted Jun 21, 2022 - 11:02 PDT
Identified
We are currently seeing a delay in Zap runs showing up in the Task history page. Tasks that need to be indexed are delayed by ~1 hour at the moment.
You might know you are impacted if you have seen results from a Zap run show up in another app, but don't see that run in your Zap history.
We have made some reallocation of resources to help catch up on runs that are delayed in showing in your task history.
Currently, there are no workarounds, but the time between a run occurring and showing up in your task history should lessen as our system catches up on indexing the Zap runs.
We will update the Status page in two hours at 11:30 PT / 18:30 UTC, but it appears we're making progress.
We appreciate your patience while we resolve the issue. Please reach out to our Support Team if you need anything: https://zapier.com/app/get-help