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

Oct 11, 2024

Transfer Existing Data Feature Unavailable in Zap Editor

Resolved - Our team has shipped a fix and this incident has been resolved. The Transfer Data feature should be back up and running in the Zap editor.

If you have any questions or are still experiencing issues, please contact our support team: https://zapier.com/app/get-help
Oct 11, 11:13 PDT

Identified - We are currently experiencing an issue where the Transfer Data feature is unavailable in the Zap Editor. This affects users who are trying to move data between apps within their Zaps using the Transfer feature for supported Zap triggers.

This incident does not impact other functionality in the Zap Editor, and all other Zaps and tasks are continuing to run and process as expected. No data loss is anticipated, and users will be able to transfer existing data once the issue is resolved.

Our team is actively investigating the issue, and we are working on mitigating the impact.

If you need further assistance, please reach out to our Support Team at the following link:
https://zapier.com/app/get-help
Oct 11, 09:58 PDT

Oct 10, 2024

No incidents reported.

Oct 9, 2024

Various apps returning errors

Resolved - On October 8, 2024, between 15:41 UTC and 18:10 UTC, an issue with certain integrations in Zapier may have impacted data passed between your Zap triggers and actions. During this period, we identified two separate issues:

1. Google Sheets Trigger and Action Failures

Some Google Sheets triggers and actions failed with error messages but have since been replayed. The data from these Zap runs should now be considered accurate.

2. Mismatched Zap Runs

Certain Zap triggers may have used data from previous Zap runs. While no data was transferred between different Zaps, connected accounts, or Zapier accounts, unintended or incorrect data may have been transferred within your Zaps.

Recommended Action

Since these Zap runs did not technically fail, we are unable to replay them or automatically identify which data may be incorrect.

If you have workflows involving the affected apps during the incident window, we strongly recommend manually reviewing any data passed between apps during this time to ensure no inaccurate data has been transferred or acted upon.

You can use Zap History with date and app filters to identify potentially impacted runs. To review this information, visit this preset Zap History view.

For any Zap runs where only the actions had erroneous data, you can utilize the Replay entire Zap run feature. This will replay an entire Zap run from the trigger step. If the trigger data is accurate, the automation will carry out as originally expected. Learn more about this feature here: Replay entire Zap run.

Next Steps

We have addressed the root cause of the issue and are implementing preventive measures to avoid future occurrences.

If you need any help or have questions about this, please contact our support team via the help page.

Oct 9, 15:28 PDT

Update - Our team has addressed this issue and a resolution has been added.
Oct 9, 15:27 PDT

Monitoring - Our team identified and addressed an issue that was causing errors and irregular data in various apps today. Some users may have run into "Unable to parse range" errors in Google Sheets specifically.

The incident was recognized at 15:12 UTC and the fix was implemented by 18:10 UTC.

For those who received the given error message, replaying the Zap should help to resolve the issue: https://help.zapier.com/hc/en-us/articles/8496241726989-Replay-failed-Zap-runs

Please note, we are monitoring the situation closely to ensure the full resolution of the incident.
Oct 8, 13:32 PDT

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.
Oct 8, 11:25 PDT

Oct 8, 2024

Oct 7, 2024

"Create New Row in Google Sheets" action populating data in the wrong sheet.

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.
Oct 7, 18:27 PDT

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.
Oct 7, 15:21 PDT

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.
Oct 7, 14:38 PDT

Oct 6, 2024

No incidents reported.

Oct 5, 2024

No incidents reported.

Oct 4, 2024

Some Zap runs stuck on 'Playing'

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
Oct 4, 14:40 PDT

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.
Oct 4, 14:16 PDT

Investigating - Some Zap runs may have been stuck in a 'Playing' status. We are investigating these runs to ensure they run to completion.
Oct 4, 13:59 PDT

Oct 3, 2024

No incidents reported.

Oct 2, 2024

Unable to map fields in Filter steps

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.
Oct 2, 08:38 PDT

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.
Oct 2, 07:49 PDT

Oct 1, 2024

Editor Instability Surrounding Filter/Path/Webhook/Code steps

Resolved - From approximately 5:40 PM to 6:03 PM UTC, a code change caused issues in the Zap editor affecting Filter, Path, Webhook, and Code steps. You may have seen some screen flickering or editor instability during this time. Additionally, you may have had issues publishing your Zaps.

The issue has since been resolved, and users should perform a hard refresh to ensure everything is functioning properly. If your Zap was published with incorrect mappings during this period, we recommend re-publishing it.

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.
Oct 1, 14:30 PDT

Sep 30, 2024

No incidents reported.

Sep 29, 2024

No incidents reported.

Sep 28, 2024

No incidents reported.

Sep 27, 2024

No incidents reported.