Zapier Status

All Systems Operational

Website Operational

Zaps Operational

Instant Triggers Operational

Polling Triggers Operational

Searches & Writes Operational

Apps Operational

Developer Platform Operational

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

System Metrics Month Week Day

Polling Triggers Reliability

Fetching

Polling Triggers Response Time

Fetching

Instant Triggers Reliability

Fetching

Instant Triggers Response Time

Fetching

Past Incidents

Dec 13, 2024

Zap History: Logs ( Beta) may not resolve/show when viewing

Resolved - The issue affecting the loading of Logs ( Beta ) feature in Zap history has been resolved. The incident occurred at approximately 16:00 UTC, and was successfully fixed by 21:30 UTC.

Our team promptly identified and solved the problem, ensuring that all Zap History logs are now displaying correctly.

If you encounter any further issues, please don't hesitate to contact our Support Team.

We thank you for your understanding and patience during this time.
Dec 13, 13:45 PST

Monitoring - Our team has now implemented a fix for our log reporting tools to clear up this Logs ( Beta ) readout.

Kindly be assured that your Zaps and runs have not been affected, this problem was only with the visuals.

We want to assure you that no data has been lost during this incident. While there was a Contact support error message popping up earlier, this has now been addressed, and the issue is resolving. However, there might be an occurrence of one-off errors, but these should be rare.

We're keeping a close eye on the situation and continue to monitor the status. If you do encounter any further issues, please do not hesitate to contact our Support Team here:
https://zapier.com/app/get-help
Dec 13, 11:33 PST

Identified - We have identified an issue affecting the Logs ( Beta ) feature in Zap history.

As a result of this problem, logs may not be displaying as expected and users might encounter an error message or an unresponsive blank panel when trying to access these logs.

The issue we have identified is related to our log reporting tools and how this displays in the history. We want to reassure you that there is no data loss associated with this incident. All Zaps and operations are functioning as normal. This issue is primarily affecting the viewing of logs in the history dashboard.

We are actively working on resolving the matter as quickly as possible. However, the issue might still occur sporadically as we enhance the log reporting function.

If you have further questions, please reach out to our Support Team here:
https://zapier.com/app/get-help
Dec 13, 10:45 PST

Investigating - As of 4:04 PM UTC, you may be seeing issues when loading the Logs ( Beta ) feature in your runs within Zap History.

Our Team is currently investigating this, and we appreciate your patience as we work to resolve this issue.

If you need further assistance, please do not hesitate to reach out to our Support Team: https://zapier.com/app/get-help.
Dec 13, 10:20 PST

Dec 12, 2024

Outage on OpenAI services

Resolved - The OpenAI team has officially resolved this incident so all related integrations are functioning again.
Dec 12, 06:27 PST

Monitoring - OpenAI services have largely recovered, and we are closely monitoring the situation to ensure the fix has fully resolved the issue.

Our team is assessing the timeframe and duration of the incident. Once confirmed, we will replay any errored Zap runs impacted by this outage.
Dec 11, 20:26 PST

Identified - Due to an outage in OpenAI services, customers may experience issues with OpenAI steps in their Zaps and AI features such as Chatbots and AI prompts.
Dec 11, 16:48 PST

Dec 11, 2024

Dec 10, 2024

No incidents reported.

Dec 9, 2024

Error on Sub-Zap Runs

Resolved - Between 10:57 AM UTC and 2:00 PM UTC, customers experienced failures when triggering Sub-Zaps, accompanied by the error message: "The app returned 'You do not have permission to perform this action.'"

The underlying issue was identified and corrected by 2:00 PM UTC. All affected Zap runs have been successfully replayed, ensuring workflows are restored without customer intervention. Thank you for your patience as our team worked to resolve this.

If you have additional questions, please contact our support team at https://zapier.com/app/get-help.
Dec 9, 07:43 PST

Identified - Customers are experiencing failures with their Zaps when triggering sub-Zaps. The error message displayed is:
"The app returned 'You do not have permission to perform this action.'”

This issue occurs even when customers own both the main Zap and the sub-Zap, suggesting the error is not related to actual permission settings. It is affecting multiple Zaps and disrupting workflows. Investigation into the root cause is ongoing.
Dec 9, 04:18 PST

Dec 8, 2024

No incidents reported.

Dec 7, 2024

No incidents reported.

Dec 6, 2024

Some Zaps experiencing trigger issues

Resolved - This issue has been resolved. If you find that some of your Zaps are failing to trigger appropriately, please cycle the Zap off and back on and test the trigger.

If you continue to run into issues, please reach out to our Support team:

https://zapier.com/app/get-help
Dec 6, 17:53 PST

Investigating - As of 12:30 AM UTC, users may see issues with some Zap triggers. Our engineering team is currently investigating the scope of the impact. We appreciate your patience as we work to resolve this issue.
Dec 6, 16:55 PST

Dec 5, 2024

Zap error notification emails delayed

Resolved - As of 12:30 AM UTC, the delay in notification emails has been resolved and all error notifications are being sent without a delay.

If you need further assistance, please do not hesitate to reach out to our Support Team: https://zapier.com/app/get-help.
Dec 5, 16:39 PST

Investigating - As of 7:40 am UTC, users may see a delay of up to 3 hours for error notifications regarding failed Zap Runs.

Zap Runs and tasks are proceeding as expected.

Our team is actively looking into this issue and trying to minimize its impact on your use of our service. We appreciate your patience as we work to resolve this.

If you need further assistance, please do not hesitate to reach out to our Support Team: https://zapier.com/app/get-help.
Dec 5, 13:31 PST

Customers trying to authenticate to the Pipedrive Integration get an error saying “App is not found”.

Resolved - The issue has been Resolved -- authentication to the Pipedrive integration should now be working

On December 5th, we experienced an issue that caused account connections to the Pipedrive integration to return errors when Zaps where trying to run.

We’ve resolved this issue and replayed all affected Zap runs. If you are still seeing that error with the authenticate to your Pipedrive account, please reconnect that account: https://zpr.io/WsZLA6GJSnSt

If you are still running with the authentication of your Pipedrive account on Zapier after that, please reach out to our Support Team: https://zapier.com/app/get-help

We appreciate your patience during this incident and apologies for any inconvenience this might have caused.
Dec 5, 11:04 PST

Update - Our engineering team has now replayed held runs that were affected by this directly.

If you still see any held runs, then there are a few quick steps we recommend.

If this has not been done yet, reconnect the app on your Pipedrive apps connection page ( https://zapier.com/app/connections/pipedrive ) in this fashion: https://help.zapier.com/hc/en-us/articles/8496290788109-Manage-your-app-connections#h_01H90TMQPTCFW2X263FFKVGHR8

If this does not reconnect fully, Add a new connection on that page, using the "Add connection" option in the upper right of the app page itself.

If a new connection is added, you'll need to ensure any Zaps using the previous Pipedrive account are updated and republished.

Once this has been reconnected in either way, you should have no issue replaying any held runs in this fashion: https://help.zapier.com/hc/en-us/articles/8496241726989-Replay-Zap-runs

We will continue to monitor this incident, to make sure all is good moving forward and will give you an update directly as soon as this is fully resolved. Please contact our Support Team here: https://zapier.com/app/get-help if you have further queries
Dec 5, 08:40 PST

Monitoring - We've identified an issue where some users are experiencing difficulty authenticating with the Pipedrive Integration. The error message displayed is "App is not found". We have implemented a fix and the integration should now be accessible again.

Our engineers have suggested trying to reconnect your Pipedrive account. If the issue persists, please attempt to add a new connection for the Pipedrive app. You can manage your connections here: https://zapier.com/app/connections/. After adding a new connection, remember to update and republish any Zaps using the previous Pipedrive account.

Please rest assured there has been no data loss as a result of this incident.

We are closely monitoring the situation to ensure the fix has fully resolved the issue. Please contact our Support Team here: https://zapier.com/app/get-help if you have further queries
Dec 5, 06:08 PST

Investigating - We are currently investigating an issue with our Pipedrive Integration.

Some customers are unable to authenticate to the Pipedrive Integration and are encountering an error displayed as “App is not found”.

This issue seems to be affecting users trying to connect to the Pipedrive Integration.

The impact of this issue is that affected users are unable to connect to Pipedrive through Zapier at this moment.

Please, if you have additional questions or need further assistance, don't hesitate to contact our support team.

We appreciate your understanding as we diligently work on resolving this issue. Updates will be provided as we receive more information.

Thank you for your patience.
Dec 5, 04:56 PST

Dec 4, 2024

No incidents reported.

Dec 3, 2024

No incidents reported.

Dec 2, 2024

No incidents reported.

Dec 1, 2024

No incidents reported.

Nov 30, 2024

No incidents reported.

Nov 29, 2024

No incidents reported.