Zap History not displaying Zap runs
major- Started
- Sep 9, 1:51 PM EDT
- Resolved
- Sep 9, 3:41 PM EDT
- Duration
- 1h 50m
Zapier's updates (4)
- investigating · Sep 9, 1:51 PM EDT
We're currently experiencing an issue where the Zap History page is not displaying recent Zap runs happening from today, September 9, 2026 starting at approximately 12:39PM EST. Zap runs are still processing normally, but can't be accessed or reviewed at the moment. We're actively investigating and will continue to update this status page with our progress. Many thanks for your patience! If you have any questions, please contact our Support team at: zapier.com/get-help.
- identified · Sep 9, 2:14 PM EDT
We've identified the root cause for Zap runs not displaying in the Zap History, and our Engineering team is working on a resolution. Zap runs are slowly appearing again in the Zap history, and we'll confirm once all Zap runs can be accessed. For any questions, please reach out to our Support team at: zapier.com/get-help.
- monitoring · Sep 9, 2:59 PM EDT
The Engineering team has implemented a fix for this issue, and Zap runs continue to load into the Zap History. Executions have not been affected: Zap runs are executing normally. However, the Zap run data was not rendering in the Zap history correctly. We appreciate your patience while we worked through this, and we will share a final update once all Zap runs are displaying successfully. If you have questions or need help, please contact our Support team at: zapier.com/get-help.
- resolved · Sep 9, 3:41 PM EDT
We have implemented a fix regarding Zap history runs not showing, so they should be available in your Zap history page now. If you have questions or need help, please contact our Support team at: [zapier.com/get-help](http://zapier.com/get-help "zapier.com/get-help").
What our checks recorded
We checked Zapier 22 times from Zapier's start time to its resolution, once every five minutes. Every one of them reached Zapier's site, so this incident did not show up as a failed page load. Our check loads the public site; it cannot see an API error or a broken feature. Median response time was 149 ms, against 218 ms over the 24 hours before. Zapier posted the incident at Sep 9, 1:51 PM EDT.
Updates are Zapier's own words from its status page (status: resolved); we never add an inferred cause.