Zapier Status

Investigating: We are currently investigating an issue with our service where some Zaps may run with a slight delay or appear in the "Playing" status within the Zap History.

As a result of this issue, you may notice a delay in your Zaps completing their tasks. We understand the inconvenience this may be causing, and we assure you that our team is diligently working to understand and resolve this issue.

The status of the issue will be continuously updated as more information becomes available to us.

Resolved: This is now resolved.

You should be able to receive those emails from Zapier going forward. Also, we are currently going through and reprocessing emails that we not able to get send out during that issue, we can ensure you get that information.

Thanks again for your patience, and if you are still running into issues with email deliverability, please reach out to Zapier Support: https://zapier.com/app/get-help

Monitoring: We have identified that this issue has affected more than just password reset emails, and is currently affecting multiple transactional email. This includes email address confirmation emails as well.

In addition, we have also implemented a fix to get these emails starting to send back out, and are monitoring the results.

Thanks again for your patience, and we'll provide any update here as soon as we can.

Identified: We've identified an issue where password reset emails are not being sent to users attempting to reset their passwords. Our team is currently working on a fix to resolve this problem as quickly as possible. We apologize for any inconvenience this may cause and appreciate your patience as we work to get this resolved. We will provide another update once the issue is fixed.

Investigating: We are currently investigating an issue with our service where some Zaps may run with a slight delay or appear in the "Playing" status within the Zap History.

As a result of this issue, you may notice a delay in your Zaps completing their tasks. We understand the inconvenience this may be causing, and we assure you that our team is diligently working to understand and resolve this issue.

The status of the issue will be continuously updated as more information becomes available to us.

Investigating: We are currently investigating an issue with our service where some Zaps may run with a slight delay or appear in the "Playing" status within the Zap History.

As a result of this issue, you may notice a delay in your Zaps completing their tasks. We understand the inconvenience this may be causing, and we assure you that our team is diligently working to understand and resolve this issue.

The status of the issue will be continuously updated as more information becomes available to us.

Investigating: We are currently investigating an issue with our service where some Zaps may run with a slight delay or appear in the "Playing" status within the Zap History.

As a result of this issue, you may notice a delay in your Zaps completing their tasks. We understand the inconvenience this may be causing, and we assure you that our team is diligently working to understand and resolve this issue.

The status of the issue will be continuously updated as more information becomes available to us.

Investigating: We are currently investigating an issue with our service where some Zaps may run with a slight delay or appear in the "Playing" status within the Zap History.

As a result of this issue, you may notice a delay in your Zaps completing their tasks. We understand the inconvenience this may be causing, and we assure you that our team is diligently working to understand and resolve this issue.

The status of the issue will be continuously updated as more information becomes available to us.

Identified: We have determined the issue is with Meta not sending webhooks to Zapier to trigger Zaps when new leads are created. We will continue to monitor this issue and work with Meta to resolve this problem.

Investigating: Meta is currently experiencing an intermittent issue whereby not all leads (webhooks) are being sent. This means the majority of leads are still initiating the Trigger, while some are being missed entirely.

Engineers from both Meta and Zapier are actively working on finding a solution.

Thank you for your patience while we and Meta aim to resolve the issue.

Investigating: Our team has identified an issue as of 9:43 am UTC that may be causing increased error rates and high latencies in live chat for both agents and customers using Zapier services. The specific error being reported is intermittent and may present as "This message failed to send. Click to retry." Currently, we are actively investigating this problem to fully understand its nature and identify a resolution. No data loss has been reported or expected due to this incident. Live chat will be disabled until the incident is resolved. We will continue to update as more information becomes available. We appreciate your patience and understanding.

Investigating: Our team has identified an issue as of 9:43 am UTC that may be causing increased error rates and high latencies in live chat for both agents and customers using Zapier services.

The specific error being reported is intermittent and may present as "This message failed to send. Click to retry."

Currently, we are actively investigating this problem to fully understand its nature and identify a resolution. No data loss has been reported or expected due to this incident.

Live chat will be disabled until the incident is resolved.

We will continue to update as more information becomes available. We appreciate your patience and understanding.

Investigating: We are continuing to investigate this issue.

Investigating: We’ve noticed that Facebook Lead Ads is experiencing issues on its platform, which is impacting your Zaps here.

The Zap runs are erroring with this message: "Error while hydrating data from Facebook Lead Ads: Unsupported get request. Object with ID 'XXXXXX' does not exist, cannot be loaded due to missing permissions"

This incident is impacting all users of the Facebook Graph API, including Zapier’s.

Specifically, we’re unable to retrieve lead information. We’ve identified that 30% of Zap runs can still run successfully.

Meta has posted about this problem here:  https://developers.facebook.com/community/threads/539279861966705/

While the root cause of this incident is outside of our control, our Engineers are working closely with our partners to resolve this as quickly as possible, and working on how to mitigate the impacts.

We recommend subscribing to updates if you haven’t already. This will allow you to follow progress on the path to resolution.

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

Investigating: We’re currently experiencing an issue with the Facebook Lead Ads Integration where users may receive the following error message:

"Error while hydrating data from Facebook Lead Ads: Unsupported get request. Object with ID '123456789' does not exist, cannot be loaded due to missing permissions"

This incident is impacting all users of the Facebook Graph API, including Zapier’s.

Specifically, we’re unable to retrieve lead information. We’ve identified that 30% of Zap runs can still run successfully.

We’re currently investigating this issue and working on how to mitigate the impacts.

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

Investigating: We are currently investigating an issue with our service where some Zaps may run with a slight delay or appear in the "Playing" status within the Zap History.

As a result of this issue, you may notice a delay in your Zaps completing their tasks. We understand the inconvenience this may be causing, and we assure you that our team is diligently working to understand and resolve this issue.

The status of the issue will be continuously updated as more information becomes available to us.