Zapier

Dec 17, 11:38 PST
Resolved – This incident has been resolved.

On Dec 16th at 4:27 PM UTC, Stripe connections began failing, and attempts to reconnect returned the following error:

‘Invalid auth connection’

Our team implemented a fix at 5:30 PM UTC on the same day.

Due to these authentication errors, some Zaps using a Stripe trigger were turned off. As of 9:30 PM UTC on Dec 16th, our team unpaused these Zaps. During the downtime, we continued to receive hooks for paused Zaps, and any failed Zap runs were replayed by our team as of Dec 17th at 6:01 PM UTC. No data was lost.

We appreciate your patience during this incident and sincerely apologize for any inconvenience caused. If you have any further questions, please don’t hesitate to reach out to our support team here: https://zapier.com/app/get-help.

Dec 16, 10:48 PST
Monitoring – We are currently looking into an issue where users experienced errors when trying to establish a connection with Stripe. The specific error message was ‘Invalid auth connection.’

We are pleased to report that we have implemented a fix and users should now be able to reconnect/enable any Zaps using Stripe without encountering the earlier problem.

If any further issues arise or you do have questions, please do not hesitate to contact our dedicated Support Team, which can be reached via this link: https://zapier.com/app/get-help

We do apologize for any inconvenience that this may have caused and appreciate your understanding as we worked to resolve the issue. We will continue to monitor the situation closely.

Dec 16, 09:00 PST
Investigating – We’re currently investigating an issue where Stripe auths are expiring, and attempts to reconnect return the following error:

‘Invalid auth connection.’

We’ll update this page with more information as it becomes available. If you have any questions, please contact our support team at https://zapier.com/app/get-help.

Dec 14, 18:09 PST
Resolved – Between 08:45 to 14:25 UTC, ActiveCampaign had an incident involving a high database load which in turn caused a delay in processing webhooks on Zapier’s end. The ActiveCampaign team has since resolved the issue and our team has collaborated with them to process the delayed hooks properly.

If you are still experiencing a delay in your ActiveCampaign Zaps, please don’t hesitate to reach out to our Support team at https://help.zapier.com/.

Dec 14, 06:14 PST
Investigating – We are investigating an issue that started today at around 08:30 UTC and involves the ActiveCampaign webhook triggers on Zapier which are failing to deliver the expected data. This is due to an outage in the ActiveCampaign API that we rely on for this service.

Users may notice a delay in the triggering of their Zaps that use ActiveCampaign webhook triggers.

There is no data loss associated with this incident. We reassure you that all data will be available once normal service has been resumed.

No workaround is available at this moment. We will notify you as soon as the situation is resolved and normal service has been reinstated.

In the meanwhile, our team is actively investigating this issue. Users who need assistance can contact our Support Team: https://zapier.com/app/get-help. We appreciate your understanding and patience as we work to resolve this disruption.

Dec 13, 13:45 PST
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, 11:33 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, 10:45 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:20 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 12, 06:27 PST
Resolved – The OpenAI team has officially resolved this incident so all related integrations are functioning again.

Dec 11, 20:26 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, 16:48 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 9, 07:43 PST
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, 04:18 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 6, 17:53 PST
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, 16:55 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 5, 16:39 PST
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, 13:31 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, 11:04 PST
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, 08:40 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, 06:08 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, 04:56 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.

Nov 21, 12:50 PST
Resolved – This incident has been resolved.

Nov 21, 12:11 PST
Monitoring – A fix has been deployed which now allows data to be imported to Zapier Tables from outside Apps again. You should now be able to import data as expected. Our team is monitoring this fix for any updates.

Nov 21, 11:48 PST
Investigating – When attempting to import data to Zapier Tables from another app like Google Sheets, an error will be returned and data won’t be able to imported. Our team is currently investigating the cause and looking for a fix.

Nov 21, 08:58 PST
Resolved – All Zap runs have been replayed and there is no data loss.

If you have any further questions, please contact our Support Team here:
https://zapier.com/app/get-help

Nov 21, 07:51 PST
Monitoring – We’ve identified an issue causing intermittent delays with Zap runs of up to an hour. This issue began at 14:24 UTC and was resolved at 15:17 UTC.

As a result, timestamps for affected Zap runs during this period may reflect delayed execution times. No data loss occurred during this time.

If you have any further questions, please contact our Support Team here:
https://zapier.com/app/get-help