Resolved after 3 hours 8 minutes, on May 20, 2026.
This issue has been resolved. The delays between Zap execution and when runs become visible in Zap History are no longer occurring. Zap History data should now be appearing in the UI as expected. As noted in our earlier update, Zap executions themselves were not impacted — this issue only affected the visibility of run data in the UI. Thank you for your patience while our team worked on this. If you continue to experience any issues, please don't hesitate to contact support: https://zapier.com/app/get-help
Update timeline
- investigating May 20, 2026, 11:57 PM UTC
We have identified delays between Zap execution and when runs become visible in Zap History. Importantly, Zap executions themselves are not failing or delayed — this issue only impacts the visibility of Zap History data in the UI. Our team is actively investigating the issue and we will continue to provide updates as soon as more information becomes available.
- resolved May 21, 2026, 03:05 AM UTC
This issue has been resolved. The delays between Zap execution and when runs become visible in Zap History are no longer occurring. Zap History data should now be appearing in the UI as expected. As noted in our earlier update, Zap executions themselves were not impacted — this issue only affected the visibility of run data in the UI. Thank you for your patience while our team worked on this. If you continue to experience any issues, please don't hesitate to contact support: https://zapier.com/app/get-help
Your product runs on more than Zapier
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services