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: <b>1. Google Sheets Trigger and Action Failures</b> 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. <b>2. Mismatched Zap Runs</b> 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. <b>Recommended Action</b> 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 <b>Zap History</b> with date and app filters to identify potentially impacted runs. To review this information, visit this preset <a href="https://zapier.com/app/history?end_datetime=2024-10-08&start_datetime=2024-10-08&app=PipedriveCLIAPI%403.16.0%2CSlackAPI%2CKeapCLIAPI%402.0.12%2CTrelloAPI%2CFollowUpBossCLIAPI%401.0.6%2CFacebookLeadsCLIAPI%401.1.2%2CCalendlyCLIAPI%402.0.3%2CAdversusDialerCLIAPI%401.19.6%2CPipefyCLIAPI%402.0.7%2CPodioAPI%2CServiceTradeCLIAPI%402.0.9%2CReliablePBXCLIAPI%402.1.0%2CTwilioAPI%2CMemberPressCLIAPI%402.2.2%2CCloseIOCLIAPI%402.1.28%2CShipStationCLIAPI%401.18.0%2CGoogleAdsCLIAPI%406.3.2%2CWooCommerceCLIAPI%402.9.3%2CAcuitySchedulingCLIAPI%401.25.3" target="_blank">Zap History view</a>. For any Zap runs where only the actions had erroneous data, you can utilize the <b>Replay entire Zap run</b> 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: <a href="https://zapier.com/blog/replay-full-zap-runs/?utm_source=google&utm_medium=cpc&utm_campaign=gaw-gbl-nua-evr-search_nb_alldev_blog_prospecting_core-ads&utm_term=&utm_content=9026832&utm_ads_campaign_id=18710515152&utm_ads_adset_id=157760468868&utm_ads_ad_id=659058345596&gad_source=1&gclid=Cj0KCQjw05i4BhDiARIsAB_2wfB1sqcyXlaPRGKWpv_BG1gqncMRPF1x2Gnhy2BjOyAPSr19XKM207waAk4HEALw_wcB" target="_blank">Replay entire Zap run</a>. <b>Next Steps</b> 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 <a href="https://zapier.com/app/get-help" target="_blank">help page</a>. </body>
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: <b>1. Google Sheets Trigger and Action Failures</b> 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. <b>2. Mismatched Zap Runs</b> 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. <b>Recommended Action</b> 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 <b>Zap History</b> with date and app filters to identify potentially impacted runs. To review this information, visit this preset <a href="https://zapier.com/app/history?end_datetime=2024-10-08&start_datetime=2024-10-08&app=PipedriveCLIAPI%403.16.0%2CSlackAPI%2CKeapCLIAPI%402.0.12%2CTrelloAPI%2CFollowUpBossCLIAPI%401.0.6%2CFacebookLeadsCLIAPI%401.1.2%2CCalendlyCLIAPI%402.0.3%2CAdversusDialerCLIAPI%401.19.6%2CPipefyCLIAPI%402.0.7%2CPodioAPI%2CServiceTradeCLIAPI%402.0.9%2CReliablePBXCLIAPI%402.1.0%2CTwilioAPI%2CMemberPressCLIAPI%402.2.2%2CCloseIOCLIAPI%402.1.28%2CShipStationCLIAPI%401.18.0%2CGoogleAdsCLIAPI%406.3.2%2CWooCommerceCLIAPI%402.9.3%2CAcuitySchedulingCLIAPI%401.25.3" target="_blank">Zap History view</a>. For any Zap runs where only the actions had erroneous data, you can utilize the <b>Replay entire Zap run</b> 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: <a href="https://zapier.com/blog/replay-full-zap-runs/?utm_source=google&utm_medium=cpc&utm_campaign=gaw-gbl-nua-evr-search_nb_alldev_blog_prospecting_core-ads&utm_term=&utm_content=9026832&utm_ads_campaign_id=18710515152&utm_ads_adset_id=157760468868&utm_ads_ad_id=659058345596&gad_source=1&gclid=Cj0KCQjw05i4BhDiARIsAB_2wfB1sqcyXlaPRGKWpv_BG1gqncMRPF1x2Gnhy2BjOyAPSr19XKM207waAk4HEALw_wcB" target="_blank">Replay entire Zap run</a>. <b>Next Steps</b> 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 <a href="https://zapier.com/app/get-help" target="_blank">help page</a>. </body>
Monitoring
Our team has addressed this issue and a resolution has been added.
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.
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.
