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 issue is now resolved, and tasks should be now playing as normal. Feel free to reach out to Zapier Support is you're still running into any issues with: https://zapier.com/app/get-help

Monitoring: We have implemented a fix to try and automatically replay these stuck runs to get them released,. We are currently monitoring the that fix to ensure that is working as intended and releasing those stuck tasks.

Investigating: Some Zap runs may have been stuck in a 'Playing' status. We are investigating these runs to ensure they run to completion.

Resolved: Between 3:39 UTC and 21:45 UTC yesterday, some customers may have experienced issues with the Google Sheets "Add Row" action, where data was written to the wrong sheet or worksheet. This impacted users with Zaps that wrote to multiple sheets using the same connected account.

We’ve resolved the issue and are currently identifying the affected customers. If your data was impacted, we’ll reach out to you soon.

Identified: We believe we have found the root cause of the issue causing data to be sent to other spreadsheets in a user's Google Sheets, and are rolling back the mechanism that caused this.

Investigating: We're currently investigating reports of the "Create New Row in Google Sheets" action populating data in the wrong spreadsheet.

We will update here as soon as we have additional information.

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: From approximately 2:10 PM to 3:00 PM UTC, a code change caused issues in the Zap editor affecting mapping fields in Filter steps.

The issue has since been resolved, and users should perform a hard refresh to ensure everything is functioning properly.

No data was lost during this time, and Zap Runs will continue as expected.

Should you encounter any further hitches with the Zap editor, we encourage you to contact our Support Team here: https://zapier.com/app/get-help.

Monitoring: From approximately 2:30 PM to 3:00 PM UTC, a code change caused issues in the Zap editor affecting mapping fields in Filter steps.

The issue has since been resolved, and users should perform a hard refresh to ensure everything is functioning properly.

No data was lost during this time, and Zap Runs will continue as expected.

Should you encounter any further hitches with the Zap editor, we encourage you to contact our Support Team here: https://zapier.com/app/get-help.

Resolved: This issue is now resolved, and tasks should be now playing as normal. Feel free to reach out to Zapier Support is you're still running into any issues with: https://zapier.com/app/get-help

Monitoring: We have implemented a fix to try and automatically replay these stuck runs to get them released,. We are currently monitoring the that fix to ensure that is working as intended and releasing those stuck tasks.

Investigating: Some Zap runs may have been stuck in a 'Playing' status. We are investigating these runs to ensure they run to completion.

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 issue is now resolved, and tasks should be now playing as normal. Feel free to reach out to Zapier Support is you're still running into any issues with: https://zapier.com/app/get-help

Monitoring: We have implemented a fix to try and automatically replay these stuck runs to get them released,. We are currently monitoring the that fix to ensure that is working as intended and releasing those stuck tasks.

Investigating: Some Zap runs may have been stuck in a 'Playing' status. We are investigating these runs to ensure they run to completion.

Resolved: Between 3:39 UTC and 21:45 UTC yesterday, some customers may have experienced issues with the Google Sheets "Add Row" action, where data was written to the wrong sheet or worksheet. This impacted users with Zaps that wrote to multiple sheets using the same connected account.

We’ve resolved the issue and are currently identifying the affected customers. If your data was impacted, we’ll reach out to you soon.

Identified: We believe we have found the root cause of the issue causing data to be sent to other spreadsheets in a user's Google Sheets, and are rolling back the mechanism that caused this.

Investigating: We're currently investigating reports of the "Create New Row in Google Sheets" action populating data in the wrong spreadsheet.

We will update here as soon as we have additional information.

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 issue is now resolved, and tasks should be now playing as normal. Feel free to reach out to Zapier Support is you're still running into any issues with: https://zapier.com/app/get-help

Monitoring: We have implemented a fix to try and automatically replay these stuck runs to get them released,. We are currently monitoring the that fix to ensure that is working as intended and releasing those stuck tasks.

Investigating: Some Zap runs may have been stuck in a 'Playing' status. We are investigating these runs to ensure they run to completion.

Resolved: Between 3:39 UTC and 21:45 UTC yesterday, some customers may have experienced issues with the Google Sheets "Add Row" action, where data was written to the wrong sheet or worksheet. This impacted users with Zaps that wrote to multiple sheets using the same connected account.

We’ve resolved the issue and are currently identifying the affected customers. If your data was impacted, we’ll reach out to you soon.

Identified: We believe we have found the root cause of the issue causing data to be sent to other spreadsheets in a user's Google Sheets, and are rolling back the mechanism that caused this.

Investigating: We're currently investigating reports of the "Create New Row in Google Sheets" action populating data in the wrong spreadsheet.

We will update here as soon as we have additional information.

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 issue is now resolved, and tasks should be now playing as normal. Feel free to reach out to Zapier Support is you're still running into any issues with: https://zapier.com/app/get-help

Monitoring: We have implemented a fix to try and automatically replay these stuck runs to get them released,. We are currently monitoring the that fix to ensure that is working as intended and releasing those stuck tasks.

Investigating: Some Zap runs may have been stuck in a 'Playing' status. We are investigating these runs to ensure they run to completion.

Resolved: Between 3:39 UTC and 21:45 UTC yesterday, some customers may have experienced issues with the Google Sheets "Add Row" action, where data was written to the wrong sheet or worksheet. This impacted users with Zaps that wrote to multiple sheets using the same connected account.

We’ve resolved the issue and are currently identifying the affected customers. If your data was impacted, we’ll reach out to you soon.

Identified: We believe we have found the root cause of the issue causing data to be sent to other spreadsheets in a user's Google Sheets, and are rolling back the mechanism that caused this.

Investigating: We're currently investigating reports of the "Create New Row in Google Sheets" action populating data in the wrong spreadsheet.

We will update here as soon as we have additional information.

Investigating: We are currently investigating an issue where various apps are returning errors or incorrect data in live Zap runs.

If your Zap returns an error, it should be resolved by replaying the Zap run.

https://help.zapier.com/hc/en-us/articles/8496241726989-Replay-failed-Zap-runs

We will update here as soon as we have additional information.

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: We are currently investigating an issue where various apps are returning errors or incorrect data in live Zap runs.

If your Zap returns an error, it should be resolved by replaying the Zap run.

https://help.zapier.com/hc/en-us/articles/8496241726989-Replay-failed-Zap-runs

We will update here as soon as we have additional information.

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 issue is now resolved, and tasks should be now playing as normal. Feel free to reach out to Zapier Support is you're still running into any issues with: https://zapier.com/app/get-help

Monitoring: We have implemented a fix to try and automatically replay these stuck runs to get them released,. We are currently monitoring the that fix to ensure that is working as intended and releasing those stuck tasks.

Investigating: Some Zap runs may have been stuck in a 'Playing' status. We are investigating these runs to ensure they run to completion.

Resolved: Between 3:39 UTC and 21:45 UTC yesterday, some customers may have experienced issues with the Google Sheets "Add Row" action, where data was written to the wrong sheet or worksheet. This impacted users with Zaps that wrote to multiple sheets using the same connected account.

We’ve resolved the issue and are currently identifying the affected customers. If your data was impacted, we’ll reach out to you soon.

Identified: We believe we have found the root cause of the issue causing data to be sent to other spreadsheets in a user's Google Sheets, and are rolling back the mechanism that caused this.

Investigating: We're currently investigating reports of the "Create New Row in Google Sheets" action populating data in the wrong spreadsheet.

We will update here as soon as we have additional information.