Monitoring - Starting May 26, there will be changes to our Gmail integration for consumer Gmail users (Gmail accounts ending in @gmail.com or @googlemail.com) that may require you to change your Zaps. More information and details on how to work with these changes can be found on our help documentation about Gmail here: https://zapier.com/help/common-problems-gmail/#my-gmail-zap-has-an-error-about-connecting-to-google-approved-or-not-approved-apps To be notified of updates regarding these changes, please subscribe to this issue.

Since our first communication with our consumer Gmail users on May 2, the list of applications approved by Google that you can send consumer Gmail data to has changed to the following:

Added to the Google-approved list: Contacts+, LionDesk CRM, Bombbomb.com.
Removed from the Google-approved list: Slack, Trello, and Asana. If you have any Zaps that send consumer Gmail data to these three apps, you will need to update them by May 26th to keep your Zaps working.

At the time of this writing, consumer Gmail users connecting Gmail to Google-approved apps on Zapier have until June 26 to re-authenticate their Google-approved apps on their Zapier account here: https://zapier.com/manage/gmail-permissions

The current list of approved apps can always be found in our help documentation about Gmail, and further changes will be posted here until final changes go live on June 26, 2019. Subscribe for instant updates.
May 22, 09:57 PDT
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
Polling Triggers Reliability ?
Fetching
Polling Triggers Response Time ?
Fetching
Instant Triggers Reliability ?
Fetching
Instant Triggers Response Time ?
Fetching
Support Queue ?
Fetching
Past Incidents
Jun 26, 2019

No incidents reported today.

Jun 25, 2019

No incidents reported.

Jun 24, 2019

No incidents reported.

Jun 23, 2019

No incidents reported.

Jun 22, 2019

No incidents reported.

Jun 21, 2019
Resolved - All of the remaining incorrect statuses for tasks, have been updated and corrected. Thanks for all of your patience while we worked on the recovery for this incident.

We are closing this now, but as always, if you have any questions, please do not hesitate to send us a message: https://zapier.com/app/contact-us
Jun 21, 11:20 PDT
Update - The Task History is still displaying incorrect statuses for some tasks from yesterday.

We are continuing to work through the list of tasks with incorrect statuses, and we are over 90% complete at this point.
Jun 21, 10:36 PDT
Update - The Task History is still displaying incorrect statuses for some tasks from yesterday.

We are continuing to work through the list of tasks with incorrect statuses, so that they can be updated in the Task History. We expect this to be fully complete within a few more hours.
Jun 21, 08:36 PDT
Update - The Task History is still displaying incorrect statuses for some tasks from earlier today. We are continuing to work through the list of tasks with incorrect statuses, so that they can be updated in the Task History.

All new tasks are running normally, and are showing correct statuses in Task History.
Jun 20, 14:04 PDT
Update - The Task History is still displaying incorrect statuses for some tasks from earlier today.

We are continuing to update those statuses in the Task History, and we will continue to update this incident as we progress.

Beyond that, tasks are running normally at this point, and any new tasks are showing correct statuses in Task History.
Jun 20, 12:22 PDT
Update - The task backlog has been fully processed at this point.

The Task History is still displaying incorrect statuses, for some tasks from today. For example, a task might still be showing as "playing" even though the actions have all been successfully completed. Or a task might not yet be showing in the task history, even though it ran.

We are continuing to update those statuses in the Task History, and we will continue to update this incident as we progress.
Jun 20, 11:21 PDT
Update - We are still processing the backlog of Tasks. The delay is under 5 minutes at this point -- so a task which triggers now will run its first action within 5 minutes from now.

Note that the Task History is currently displaying incorrect statuses, for some tasks from today. For example, a task might still be showing as "playing" even though the actions have all been successfully completed. Or a task might not yet be showing in the task history, even though it ran.

We are starting to update those statuses in the Task History now. We will continue to update this incident as we progress.
Jun 20, 10:25 PDT
Update - We are still processing the backlog of Tasks. The delay is roughly 40 minutes at this point -- so a task which triggers now will run its first action 40 minutes from now.

We will continue to update this incident as we work through the backlog.
Jun 20, 09:20 PDT
Monitoring - We are still processing the backlog of Tasks, and that is approximately 65% complete at this point. We will update this incident again once that is fully complete.

Zaps will still continue to trigger, and action steps will be automatically queued. No data has been lost because of the incident.
Jun 20, 08:19 PDT
Update - We are still processing the Tasks that have been queued because of the incident earlier today. Zaps will still continue to trigger, and action steps will be automatically queued. No data has been lost because of the incident.

We're sorry about the disruption, and appreciate your patience as we work through the backlog of Tasks.
Jun 20, 06:53 PDT
Update - We're continuing to process the Tasks that have been queued because of the incident earlier today, and we hope to get through the Task queue soon. We're sorry about the disruption, and appreciate your patience as we get through the queue. Zaps will continue to receive trigger data, and no data has been lost because of the incident.
Jun 20, 05:58 PDT
Update - Thanks for your patience as we get through the queue of Tasks and process them. We're continuing to work through the queue caused by the incident earlier today. Any affected Zaps should continue to trigger and be processed in the queue, and no data has been lost.

We're really sorry for the delay and disruption this cases. We'll continue to monitor the situation, and post updates here as we get them.
Jun 20, 04:31 PDT
Update - We're seeing a reduction in the queue of Tasks as they're beginning to be played, and we hope to have them all processed soon. We're sorry about the trouble & delay in processing Tasks today, and we thank you for your patience as we're working through them.
Jun 20, 03:27 PDT
Update - We're continuing to process the queue of delayed Tasks caused by the earlier issues. We hope to have processed all remaining Tasks soon, and we'll continue to monitor the situation.
Jun 20, 02:35 PDT
Identified - We have identified the cause of the delay in Tasks processing, and we've addressed the issue. Delayed Tasks are now beginning to be processed, and we hope to be back-to-normal soon. We're sorry for the trouble caused by these delays.

We'll continue to monitor the situation, and we'll post an update here once fully resolved.
Jun 20, 02:01 PDT
Investigating - We are currently investigating this issue.
Jun 20, 00:59 PDT
Jun 19, 2019

No incidents reported.

Jun 18, 2019
Resolved - Google has confirmed that the issue with Google Calendar has been resolved. Any tasks that hit errors with Google Calendar steps should be replayable. Thanks for your patience!
Jun 18, 11:09 PDT
Investigating - Google Calendar is having some trouble today. Many folks are not able to log into their Calendars at all. This also means that some Zaps are not able to see Google Calendar info normally. We're investigating and will post updates here.

For additional information, Google is sharing updates on their status page as well: https://www.google.com/appsstatus#hl=en&v=status
Jun 18, 08:30 PDT
Jun 17, 2019

No incidents reported.

Jun 16, 2019

No incidents reported.

Jun 15, 2019

No incidents reported.

Jun 14, 2019

No incidents reported.

Jun 13, 2019

No incidents reported.

Jun 12, 2019

No incidents reported.