Time: Oct. 21, 2024, 11:06 a.m.

Status: Resolved

Update: This issue should now be resolved and all services are restored to normal functionality.

Time: Oct. 21, 2024, 10:47 a.m.

Status: Investigating

Update: 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. Users experiencing this issue can find help via our support team at: https://zapier.com/app/get-help. We will continue to update as more information becomes available. We appreciate your patience and understanding.

Time: Oct. 21, 2024, 10:44 a.m.

Status: Investigating

Update: 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.

Time: Oct. 21, 2024, 10:44 a.m.

Status: Investigating

Update: 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.

Time: Oct. 11, 2024, 6:13 p.m.

Status: Resolved

Update: 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

Time: Oct. 11, 2024, 4:58 p.m.

Status: Identified

Update: 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

Time: Oct. 9, 2024, 10:28 p.m.

Status: Resolved

Update: 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>Impacted Apps</b> This issue may have affected Zap runs during the time period, involving the following apps: - Pipedrive - Slack - Keap Max Classic - Trello - Follow Up Boss - Facebook Lead Ads - Calendly - Zendesk - Adversus Dialer - OpenSolar - Pipefy - Podio - ServiceTrade - Reliable PBX - Twilio - MemberPress - Close - ShipStation - Google Ads - WooCommerce - Acuity Scheduling - Salesforce <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>

Time: Oct. 9, 2024, 10:27 p.m.

Status: Monitoring

Update: Our team has addressed this issue and a resolution has been added.

Time: Oct. 8, 2024, 8:32 p.m.

Status: Monitoring

Update: 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.

Time: Oct. 8, 2024, 6:25 p.m.

Status: Investigating

Update: We are currently investigating an issue where various apps are returning errors or incorrect data. If your Zap run errors, 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.

Time: Oct. 8, 2024, 1:27 a.m.

Status: Resolved

Update: 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.

Time: Oct. 7, 2024, 10:21 p.m.

Status: Identified

Update: 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.

Time: Oct. 7, 2024, 9:38 p.m.

Status: Investigating

Update: 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.