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 incident, which previously resulted in 503 errors navigating the zapier.com website, has now been resolved.

Monitoring: Our team has identified the issue and we've implemented a fix. Users should no longer be experiencing login issues and errors should no longer be present when accessing any pages within Zapier.com.

We're now monitoring this outage for any further problems.

If you have any questions or if you're still running into issues, please reach out to our Support team:

https://zapier.com/app/get-help

Investigating: Our team has been made aware of an issue affecting the ability to login to Zapier.com.

Users may experience pages not loading or endlessly loading. This issue may also present itself as 503 errors when accessing the site.

We're currently investigating this issue and we'll provide an update as soon as we have one available.

If you have any questions, you can reach out to our Support team:

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.

Resolved: This incident, which previously resulted in errors in Facebook Lead Ads triggers, has now been resolved.

Meta has confirmed that a fix has been released and our Engineers have started replayed the runs. Any remaining errors will be replayed and all leads should be processed successfully.

If you have any questions or need additional clarification, you can contact our Support team at https://zapier.com/help

We appreciate your patience while we worked on resolving this issue. Thank you.

Monitoring: Our engineers are working to replay any Zap steps which were impacted by this incident to ensure that your workflows are completed. We have subsequently seen a significant reduction in the prevalence of the error.

However, some attempts to collect lead information are still seeing instances of the error.

Monitoring: Meta have advised us that a fix for the issue has been deployed, and we have subsequently seen a significant reduction in the prevalence of the error.

However, some attempts to collect lead information are still seeing instances of the error.

We are continuing to work with Meta and will update our status page again when the issue is completely resolved.

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. More 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 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’ve noticed that Facebook Lead Ads is experiencing issues on its platform, which is impacting Facebook Lead Ad Zaps.

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"

Our team is currently investigating and we'll provide an update as soon as we can.

If you have any questions, please reach out to our support team:

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.

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: 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: Users with connections for Facebook Conversions and Facebook Conversions (for Business) have been reporting issues with the app disconnecting. Upon attempting to authenticate, they are met with the following error:

"API calls from the server require an appsecret_proof argument"

This issue has been brought to the attention of the partner team in charge of those apps and we are awaiting further information from them on options for a fix.

We apologize for the inconvenience but thank you for your patience while those involved continued the investigation.

Investigating: Users with connections for Facebook Conversions and Facebook Conversions (for Business) have been reporting issues with the app disconnecting. Upon attempting to authenticate, they are met with the following error:

"API calls from the server require an appsecret_proof argument"

This issue has been brought to the attention of the partner team in charge of those apps and we are awaiting further information from them on options for a fix.

We apologize for the inconvenience but thank you for your patience while those involved continued the investigation.

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.