UiPath Status

Resolved: The issue is resolved and sign-in and access checks in Automation Cloud in Europe are performing normally. Impact: No ongoing user impact.

Monitoring: A fix has been implemented and sign-in and access-check performance in Automation Cloud in Europe is returning to normal. Impact: Some users may still notice slightly slower responses while the system stabilizes.

Investigating: We have identified degraded performance affecting sign-in and access checks in Automation Cloud in Europe. Impact: Users may experience slower sign-in, token refresh and page loads, and some actions that check permissions may be slower than usual. Services remain available.

Postmortem: Customer impact

On 9 November 2026, from 08:51 UTC, Integration Service connections to Google Sheets and Google Docs that use the UiPath-managed Google application failed to authenticate. Affected connections could not refresh their access token or reconnect, and automations that used them failed with an "invalid_client" error. At the peak, connections in about 450 organizations across all commercial regions were affected.

Service was restored region by region. The first region recovered at 12:14 UTC and all regions by 13:08 UTC. The impact lasted 4 hours and 17 minutes.

Google Drive and Gmail connections, and Sheets or Docs connections that use a customer-owned Google application, were not affected. No customer data was lost or changed. Existing connections recovered on their own once their region was fixed. A connection that a customer tried to re-authorize during the outage, and that failed, needs one Reconnect.

Root cause

On 3 November, as part of a credential rotation, we replaced the credential of the Google application that UiPath uses for the Google Drive connector and moved all Google Drive connections to the new credential.

The same Google application is also used by the Google Sheets and Google Docs connectors, but our inventory listed it under Google Drive only. Sheets and Docs connections were therefore not moved to the new credential and kept using the old one, which still worked.

On 9 November at 08:51 UTC the old credential was deleted. From that moment, every Sheets and Docs connection on the UiPath-managed application could no longer obtain a new access token. The credential was deleted rather than disabled, so it could not be turned back on while we fixed the connections.

Detection

Our monitoring raised an alert for a high authentication failure rate on the Google Sheets connector at 09:38 UTC, 47 minutes after the failures began. The alert took this long because it measures the failure rate over a three-hour window, and token refresh failures were not covered by our faster alert on failed connection creation. Our engineers identified the shared credential as the cause at about 10:45 UTC. The first customer report reached our support team at 10:43 UTC.

Response

• 11:23 UTC: the current credential was written into the Sheets and Docs configuration for the commercial regions.
• 11:30 UTC: we declared an incident, and posted on the status page at 11:44 UTC.
• 11:47 UTC: the first region received the new configuration. New connections and reconnects in that region worked from this point.
• 12:14 UTC: all existing Sheets and Docs connections in the first region were moved to the new credential, and no failures were seen there after 12:00 UTC.
• 13:08 UTC: all regions were complete. Over 66,000 Sheets connections and 3,300 Docs connections were updated, with no failures after 13:08 UTC.
• 13:18 UTC: the status page incident was resolved.
• 13:55 UTC: the PCI regions were checked and had no affected connections.

Follow up

• Keep an inventory that maps each vendor application credential to every connector that uses it, and verify it against the stored credential before any rotation, so a shared credential cannot be missed again.
• Disable an old credential for a waiting period before deleting it, so it can be restored at once if a dependency was missed.
• Alert on authentication failures during token refresh, not only on failed connection creation, so this kind of failure is detected within minutes.
• Update our maintenance process so that all regions are updated at the same time.

Resolved: The issue affecting Google Sheets and Google Docs connections in Integration Service across multiple regions has been fully resolved, and all affected functionality is operating normally.

Identified: A fix is being rolled out for the authentication failures affecting Google Sheets and Google Docs connections in Integration Service across multiple regions.

Identified: We have identified the cause of the issue impacting Google Sheets and Google Docs connections failing in Integration Service for Multi-region and are working on mitigation. Impact: Users may experience Authentication failures for Google docs and sheets. Additional updates will be provided as we move toward resolution.

Resolved: Integration Service triggers for Microsoft Outlook 365 have fully recovered in all regions, including Australia, India and Singapore, following the resolution of the upstream provider outage. Trigger processing has been running normally since 13:40 UTC on November 13. No events were lost; emails received during the outage have been processed. This incident is resolved.

Identified: Microsoft 365 is recovering, and Outlook triggers have resumed in Japan, Europe, the United States, the United Kingdom and Canada.

Outlook triggers are still failing in Australia, India and Singapore because of the ongoing Microsoft 365 issue in those regions. They will recover as Microsoft restores service there.

Triggers for other connections are running normally in all regions.

No events have been lost. Emails received during the outage are being processed now that Microsoft 365 is available again, and the remaining regions will catch up automatically once Microsoft recovers.

We'll post another update when the remaining regions recover

Identified: We've deployed a fix in the US and EU regions that reduces the impact of the ongoing Microsoft 365 outage on other integrations. Triggers for other connections should now be processed with normal or much shorter delays.

Outlook triggers are still delayed or failing, and will stay that way until Microsoft 365 recovers. No events have been lost. Any pending Outlook events will be processed automatically once Microsoft's service is restored.

We're continuing to monitor and will post another update as the situation progresses.

Identified: We've deployed a fix in the US and EU regions that reduces the impact of the ongoing Microsoft 365 outage on other integrations. Triggers for other connections should now be processed with normal or much shorter delays.

Outlook triggers are still delayed or failing, and will stay that way until Microsoft 365 recovers. No events have been lost. Any pending Outlook events will be processed automatically once Microsoft's service is restored.

We're continuing to monitor and will post another update as the situation progresses.

Identified: We've deployed a fix in the US and EU regions that reduces the impact of the ongoing Microsoft 365 outage on other integrations. Triggers for other connections should now be processed with normal or much shorter delays.

Outlook triggers are still delayed or failing, and will stay that way until Microsoft 365 recovers. No events have been lost. Any pending Outlook events will be processed automatically once Microsoft's service is restored.

We're continuing to monitor and will post another update as the situation progresses.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in Integration Service in the United States remain delayed due to the ongoing upstream provider outage. Europe, Community, Australia and India remain recovered. No trigger events are lost; they will be processed automatically once the provider recovers.

Identified: Event triggers in Integration Service have recovered in Europe, Community, Australia and India. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in the United States are still delayed due to the ongoing upstream provider outage. No trigger events are lost; they will be processed automatically once the provider recovers.

Identified: The cause of delayed event triggers in Integration Service in the United States, Europe, Community, Australia and India has been identified as an upstream provider outage. Impact: Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors are delayed. Triggers for other connectors may also experience some delay. No trigger events are lost; they will be processed automatically once the provider recovers.

Resolved: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining has remained stable in all regions since recovery, following the resolution of the upstream provider outage. All delayed emails have been synchronized and no emails were lost. This incident is resolved.

Monitoring: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining has recovered in all regions. We're monitoring to make sure it remains stable.

Identified: The upstream provider has largely recovered, and synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining has caught up in most regions. Email sync in the United States, Canada, Australia and Japan has been running normally since 12:06 PM UTC

As mailbox activity increases with the start of the business day in the US and Canada, sync delays could build up again in those regions while the provider is still limiting traffic. We are monitoring closely.

In Europe and Singapore, synchronization is still catching up. The backlog is decreasing slowly, so delays will continue there for now.

No emails are lost. All delayed emails will be synchronized automatically. We'll post another update when Europe and Singapore have recovered.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: We are continuing to monitor the upstream provider outage that is delaying the synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining. New emails may still be delayed in appearing in Communications Mining. No emails are lost; synchronization will catch up automatically once the provider recovers.

Identified: We have identified an upstream provider outage that is delaying the synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining. Impact: New emails may be delayed in appearing in Communications Mining. No emails are lost; synchronization will catch up automatically once the provider recovers.

Resolved: The third-party provider issue that caused some Serverless jobs using Microsoft 365 activities to fail has been resolved. Microsoft 365 activities in Serverless jobs are working normally again.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Postmortem: Customer impact On 9 November 2026, from 15:11 UTC, some Studio Web users in the Europe region could not publish or deploy projects. Service was fully restored at 17:10 UTC. Other Studio Web features, such as editing, debugging and running projects, kept working. Your projects and data were not affected. Publish and deploy requests stopped before anything was published, and no project was lost or changed.

Root cause Studio Web asks a backend service which version of the publishing and deployment experience to load. That version is set separately for each server cluster. During routine maintenance, traffic in the Europe region moved to a new set of clusters at 15:05 UTC. Our release process had not written the version setting to those clusters, so they fell back to an outdated default that did not recognize the current release. Studio Web received an empty version and stopped, as designed, so publish and deploy failed.

Detection Our monitoring system raised an alert at 15:28 UTC, 17 minutes after the failures began. Our engineers confirmed customer impact at 15:42 UTC.

Response

• 16:31 UTC: we declared an incident.
• 16:45 UTC: we posted an update on the status page.
• 16:57 UTC: we added the missing version setting to the new clusters, copied from the clusters that were working.
• 17:10 UTC: the fix was fully deployed, and we confirmed that publish and deploy worked again.

Follow up

• Write the version setting to every active cluster in every region on each release, including new and standby clusters. This is complete.
• Make the default setting serve a working version, so a cluster without its own setting still works. This is complete.
• Set the version automatically for every cluster that serves traffic, so moving traffic between clusters can't leave a cluster without a version.
• Declare an incident as soon as monitoring confirms customer impact, and make infrastructure changes visible to our on-call engineers.

Resolved: This issue has been resolved. Some users were unable to publish projects from Studio Web. The fix is fully deployed and publishing is working normally again. We apologize for the inconvenience.

Identified: We have identified the cause of the issue preventing some users from publishing projects from Studio Web, and we are rolling out a fix. Publishing may keep failing until the fix is fully deployed.

Investigating: We are investigating an issue where some users can't publish projects from Studio Web. Other actions in Studio Web don't appear to be affected. The issue started at about 16:30 UTC on November 9, 2026, and our engineering teams are working to find the cause.

Postmortem: Customer impact

On 9 November 2026, from 08:51 UTC, Integration Service connections to Google Sheets and Google Docs that use the UiPath-managed Google application failed to authenticate. Affected connections could not refresh their access token or reconnect, and automations that used them failed with an "invalid_client" error. At the peak, connections in about 450 organizations across all commercial regions were affected.

Service was restored region by region. The first region recovered at 12:14 UTC and all regions by 13:08 UTC. The impact lasted 4 hours and 17 minutes.

Google Drive and Gmail connections, and Sheets or Docs connections that use a customer-owned Google application, were not affected. No customer data was lost or changed. Existing connections recovered on their own once their region was fixed. A connection that a customer tried to re-authorize during the outage, and that failed, needs one Reconnect.

Root cause

On 3 November, as part of a credential rotation, we replaced the credential of the Google application that UiPath uses for the Google Drive connector and moved all Google Drive connections to the new credential.

The same Google application is also used by the Google Sheets and Google Docs connectors, but our inventory listed it under Google Drive only. Sheets and Docs connections were therefore not moved to the new credential and kept using the old one, which still worked.

On 9 November at 08:51 UTC the old credential was deleted. From that moment, every Sheets and Docs connection on the UiPath-managed application could no longer obtain a new access token. The credential was deleted rather than disabled, so it could not be turned back on while we fixed the connections.

Detection

Our monitoring raised an alert for a high authentication failure rate on the Google Sheets connector at 09:38 UTC, 47 minutes after the failures began. The alert took this long because it measures the failure rate over a three-hour window, and token refresh failures were not covered by our faster alert on failed connection creation. Our engineers identified the shared credential as the cause at about 10:45 UTC. The first customer report reached our support team at 10:43 UTC.

Response

• 11:23 UTC: the current credential was written into the Sheets and Docs configuration for the commercial regions.
• 11:30 UTC: we declared an incident, and posted on the status page at 11:44 UTC.
• 11:47 UTC: the first region received the new configuration. New connections and reconnects in that region worked from this point.
• 12:14 UTC: all existing Sheets and Docs connections in the first region were moved to the new credential, and no failures were seen there after 12:00 UTC.
• 13:08 UTC: all regions were complete. Over 66,000 Sheets connections and 3,300 Docs connections were updated, with no failures after 13:08 UTC.
• 13:18 UTC: the status page incident was resolved.
• 13:55 UTC: the PCI regions were checked and had no affected connections.

Follow up

• Keep an inventory that maps each vendor application credential to every connector that uses it, and verify it against the stored credential before any rotation, so a shared credential cannot be missed again.
• Disable an old credential for a waiting period before deleting it, so it can be restored at once if a dependency was missed.
• Alert on authentication failures during token refresh, not only on failed connection creation, so this kind of failure is detected within minutes.
• Update our maintenance process so that all regions are updated at the same time.

Resolved: The issue affecting Google Sheets and Google Docs connections in Integration Service across multiple regions has been fully resolved, and all affected functionality is operating normally.

Identified: A fix is being rolled out for the authentication failures affecting Google Sheets and Google Docs connections in Integration Service across multiple regions.

Identified: We have identified the cause of the issue impacting Google Sheets and Google Docs connections failing in Integration Service for Multi-region and are working on mitigation. Impact: Users may experience Authentication failures for Google docs and sheets. Additional updates will be provided as we move toward resolution.

Resolved: Integration Service triggers for Microsoft Outlook 365 have fully recovered in all regions, including Australia, India and Singapore, following the resolution of the upstream provider outage. Trigger processing has been running normally since 13:40 UTC on November 13. No events were lost; emails received during the outage have been processed. This incident is resolved.

Identified: Microsoft 365 is recovering, and Outlook triggers have resumed in Japan, Europe, the United States, the United Kingdom and Canada.

Outlook triggers are still failing in Australia, India and Singapore because of the ongoing Microsoft 365 issue in those regions. They will recover as Microsoft restores service there.

Triggers for other connections are running normally in all regions.

No events have been lost. Emails received during the outage are being processed now that Microsoft 365 is available again, and the remaining regions will catch up automatically once Microsoft recovers.

We'll post another update when the remaining regions recover

Identified: We've deployed a fix in the US and EU regions that reduces the impact of the ongoing Microsoft 365 outage on other integrations. Triggers for other connections should now be processed with normal or much shorter delays.

Outlook triggers are still delayed or failing, and will stay that way until Microsoft 365 recovers. No events have been lost. Any pending Outlook events will be processed automatically once Microsoft's service is restored.

We're continuing to monitor and will post another update as the situation progresses.

Identified: We've deployed a fix in the US and EU regions that reduces the impact of the ongoing Microsoft 365 outage on other integrations. Triggers for other connections should now be processed with normal or much shorter delays.

Outlook triggers are still delayed or failing, and will stay that way until Microsoft 365 recovers. No events have been lost. Any pending Outlook events will be processed automatically once Microsoft's service is restored.

We're continuing to monitor and will post another update as the situation progresses.

Identified: We've deployed a fix in the US and EU regions that reduces the impact of the ongoing Microsoft 365 outage on other integrations. Triggers for other connections should now be processed with normal or much shorter delays.

Outlook triggers are still delayed or failing, and will stay that way until Microsoft 365 recovers. No events have been lost. Any pending Outlook events will be processed automatically once Microsoft's service is restored.

We're continuing to monitor and will post another update as the situation progresses.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in Integration Service in the United States remain delayed due to the ongoing upstream provider outage. Europe, Community, Australia and India remain recovered. No trigger events are lost; they will be processed automatically once the provider recovers.

Identified: Event triggers in Integration Service have recovered in Europe, Community, Australia and India. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in the United States are still delayed due to the ongoing upstream provider outage. No trigger events are lost; they will be processed automatically once the provider recovers.

Identified: The cause of delayed event triggers in Integration Service in the United States, Europe, Community, Australia and India has been identified as an upstream provider outage. Impact: Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors are delayed. Triggers for other connectors may also experience some delay. No trigger events are lost; they will be processed automatically once the provider recovers.

Resolved: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining has remained stable in all regions since recovery, following the resolution of the upstream provider outage. All delayed emails have been synchronized and no emails were lost. This incident is resolved.

Monitoring: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining has recovered in all regions. We're monitoring to make sure it remains stable.

Identified: The upstream provider has largely recovered, and synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining has caught up in most regions. Email sync in the United States, Canada, Australia and Japan has been running normally since 12:06 PM UTC

As mailbox activity increases with the start of the business day in the US and Canada, sync delays could build up again in those regions while the provider is still limiting traffic. We are monitoring closely.

In Europe and Singapore, synchronization is still catching up. The backlog is decreasing slowly, so delays will continue there for now.

No emails are lost. All delayed emails will be synchronized automatically. We'll post another update when Europe and Singapore have recovered.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: We are continuing to monitor the upstream provider outage that is delaying the synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining. New emails may still be delayed in appearing in Communications Mining. No emails are lost; synchronization will catch up automatically once the provider recovers.

Identified: We have identified an upstream provider outage that is delaying the synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining. Impact: New emails may be delayed in appearing in Communications Mining. No emails are lost; synchronization will catch up automatically once the provider recovers.

Resolved: The third-party provider issue that caused some Serverless jobs using Microsoft 365 activities to fail has been resolved. Microsoft 365 activities in Serverless jobs are working normally again.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Postmortem: Customer impact

On 9 November 2026, from 08:51 UTC, Integration Service connections to Google Sheets and Google Docs that use the UiPath-managed Google application failed to authenticate. Affected connections could not refresh their access token or reconnect, and automations that used them failed with an "invalid_client" error. At the peak, connections in about 450 organizations across all commercial regions were affected.

Service was restored region by region. The first region recovered at 12:14 UTC and all regions by 13:08 UTC. The impact lasted 4 hours and 17 minutes.

Google Drive and Gmail connections, and Sheets or Docs connections that use a customer-owned Google application, were not affected. No customer data was lost or changed. Existing connections recovered on their own once their region was fixed. A connection that a customer tried to re-authorize during the outage, and that failed, needs one Reconnect.

Root cause

On 3 November, as part of a credential rotation, we replaced the credential of the Google application that UiPath uses for the Google Drive connector and moved all Google Drive connections to the new credential.

The same Google application is also used by the Google Sheets and Google Docs connectors, but our inventory listed it under Google Drive only. Sheets and Docs connections were therefore not moved to the new credential and kept using the old one, which still worked.

On 9 November at 08:51 UTC the old credential was deleted. From that moment, every Sheets and Docs connection on the UiPath-managed application could no longer obtain a new access token. The credential was deleted rather than disabled, so it could not be turned back on while we fixed the connections.

Detection

Our monitoring raised an alert for a high authentication failure rate on the Google Sheets connector at 09:38 UTC, 47 minutes after the failures began. The alert took this long because it measures the failure rate over a three-hour window, and token refresh failures were not covered by our faster alert on failed connection creation. Our engineers identified the shared credential as the cause at about 10:45 UTC. The first customer report reached our support team at 10:43 UTC.

Response

• 11:23 UTC: the current credential was written into the Sheets and Docs configuration for the commercial regions.
• 11:30 UTC: we declared an incident, and posted on the status page at 11:44 UTC.
• 11:47 UTC: the first region received the new configuration. New connections and reconnects in that region worked from this point.
• 12:14 UTC: all existing Sheets and Docs connections in the first region were moved to the new credential, and no failures were seen there after 12:00 UTC.
• 13:08 UTC: all regions were complete. Over 66,000 Sheets connections and 3,300 Docs connections were updated, with no failures after 13:08 UTC.
• 13:18 UTC: the status page incident was resolved.
• 13:55 UTC: the PCI regions were checked and had no affected connections.

Follow up

• Keep an inventory that maps each vendor application credential to every connector that uses it, and verify it against the stored credential before any rotation, so a shared credential cannot be missed again.
• Disable an old credential for a waiting period before deleting it, so it can be restored at once if a dependency was missed.
• Alert on authentication failures during token refresh, not only on failed connection creation, so this kind of failure is detected within minutes.
• Update our maintenance process so that all regions are updated at the same time.

Resolved: The issue affecting Google Sheets and Google Docs connections in Integration Service across multiple regions has been fully resolved, and all affected functionality is operating normally.

Identified: A fix is being rolled out for the authentication failures affecting Google Sheets and Google Docs connections in Integration Service across multiple regions.

Identified: We have identified the cause of the issue impacting Google Sheets and Google Docs connections failing in Integration Service for Multi-region and are working on mitigation. Impact: Users may experience Authentication failures for Google docs and sheets. Additional updates will be provided as we move toward resolution.

Resolved: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining has remained stable in all regions since recovery, following the resolution of the upstream provider outage. All delayed emails have been synchronized and no emails were lost. This incident is resolved.

Monitoring: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining has recovered in all regions. We're monitoring to make sure it remains stable.

Identified: The upstream provider has largely recovered, and synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining has caught up in most regions. Email sync in the United States, Canada, Australia and Japan has been running normally since 12:06 PM UTC

As mailbox activity increases with the start of the business day in the US and Canada, sync delays could build up again in those regions while the provider is still limiting traffic. We are monitoring closely.

In Europe and Singapore, synchronization is still catching up. The backlog is decreasing slowly, so delays will continue there for now.

No emails are lost. All delayed emails will be synchronized automatically. We'll post another update when Europe and Singapore have recovered.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: We are continuing to monitor the upstream provider outage that is delaying the synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining. New emails may still be delayed in appearing in Communications Mining. No emails are lost; synchronization will catch up automatically once the provider recovers.

Identified: We have identified an upstream provider outage that is delaying the synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining. Impact: New emails may be delayed in appearing in Communications Mining. No emails are lost; synchronization will catch up automatically once the provider recovers.

Resolved: The third-party provider issue that caused some Serverless jobs using Microsoft 365 activities to fail has been resolved. Microsoft 365 activities in Serverless jobs are working normally again.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Postmortem: Customer impact

On 9 November 2026, from 08:51 UTC, Integration Service connections to Google Sheets and Google Docs that use the UiPath-managed Google application failed to authenticate. Affected connections could not refresh their access token or reconnect, and automations that used them failed with an "invalid_client" error. At the peak, connections in about 450 organizations across all commercial regions were affected.

Service was restored region by region. The first region recovered at 12:14 UTC and all regions by 13:08 UTC. The impact lasted 4 hours and 17 minutes.

Google Drive and Gmail connections, and Sheets or Docs connections that use a customer-owned Google application, were not affected. No customer data was lost or changed. Existing connections recovered on their own once their region was fixed. A connection that a customer tried to re-authorize during the outage, and that failed, needs one Reconnect.

Root cause

On 3 November, as part of a credential rotation, we replaced the credential of the Google application that UiPath uses for the Google Drive connector and moved all Google Drive connections to the new credential.

The same Google application is also used by the Google Sheets and Google Docs connectors, but our inventory listed it under Google Drive only. Sheets and Docs connections were therefore not moved to the new credential and kept using the old one, which still worked.

On 9 November at 08:51 UTC the old credential was deleted. From that moment, every Sheets and Docs connection on the UiPath-managed application could no longer obtain a new access token. The credential was deleted rather than disabled, so it could not be turned back on while we fixed the connections.

Detection

Our monitoring raised an alert for a high authentication failure rate on the Google Sheets connector at 09:38 UTC, 47 minutes after the failures began. The alert took this long because it measures the failure rate over a three-hour window, and token refresh failures were not covered by our faster alert on failed connection creation. Our engineers identified the shared credential as the cause at about 10:45 UTC. The first customer report reached our support team at 10:43 UTC.

Response

• 11:23 UTC: the current credential was written into the Sheets and Docs configuration for the commercial regions.
• 11:30 UTC: we declared an incident, and posted on the status page at 11:44 UTC.
• 11:47 UTC: the first region received the new configuration. New connections and reconnects in that region worked from this point.
• 12:14 UTC: all existing Sheets and Docs connections in the first region were moved to the new credential, and no failures were seen there after 12:00 UTC.
• 13:08 UTC: all regions were complete. Over 66,000 Sheets connections and 3,300 Docs connections were updated, with no failures after 13:08 UTC.
• 13:18 UTC: the status page incident was resolved.
• 13:55 UTC: the PCI regions were checked and had no affected connections.

Follow up

• Keep an inventory that maps each vendor application credential to every connector that uses it, and verify it against the stored credential before any rotation, so a shared credential cannot be missed again.
• Disable an old credential for a waiting period before deleting it, so it can be restored at once if a dependency was missed.
• Alert on authentication failures during token refresh, not only on failed connection creation, so this kind of failure is detected within minutes.
• Update our maintenance process so that all regions are updated at the same time.

Resolved: The issue affecting Google Sheets and Google Docs connections in Integration Service across multiple regions has been fully resolved, and all affected functionality is operating normally.

Identified: A fix is being rolled out for the authentication failures affecting Google Sheets and Google Docs connections in Integration Service across multiple regions.

Identified: We have identified the cause of the issue impacting Google Sheets and Google Docs connections failing in Integration Service for Multi-region and are working on mitigation. Impact: Users may experience Authentication failures for Google docs and sheets. Additional updates will be provided as we move toward resolution.

Resolved: Integration Service triggers for Microsoft Outlook 365 have fully recovered in all regions, including Australia, India and Singapore, following the resolution of the upstream provider outage. Trigger processing has been running normally since 13:40 UTC on November 13. No events were lost; emails received during the outage have been processed. This incident is resolved.

Identified: Microsoft 365 is recovering, and Outlook triggers have resumed in Japan, Europe, the United States, the United Kingdom and Canada.

Outlook triggers are still failing in Australia, India and Singapore because of the ongoing Microsoft 365 issue in those regions. They will recover as Microsoft restores service there.

Triggers for other connections are running normally in all regions.

No events have been lost. Emails received during the outage are being processed now that Microsoft 365 is available again, and the remaining regions will catch up automatically once Microsoft recovers.

We'll post another update when the remaining regions recover

Identified: We've deployed a fix in the US and EU regions that reduces the impact of the ongoing Microsoft 365 outage on other integrations. Triggers for other connections should now be processed with normal or much shorter delays.

Outlook triggers are still delayed or failing, and will stay that way until Microsoft 365 recovers. No events have been lost. Any pending Outlook events will be processed automatically once Microsoft's service is restored.

We're continuing to monitor and will post another update as the situation progresses.

Identified: We've deployed a fix in the US and EU regions that reduces the impact of the ongoing Microsoft 365 outage on other integrations. Triggers for other connections should now be processed with normal or much shorter delays.

Outlook triggers are still delayed or failing, and will stay that way until Microsoft 365 recovers. No events have been lost. Any pending Outlook events will be processed automatically once Microsoft's service is restored.

We're continuing to monitor and will post another update as the situation progresses.

Identified: We've deployed a fix in the US and EU regions that reduces the impact of the ongoing Microsoft 365 outage on other integrations. Triggers for other connections should now be processed with normal or much shorter delays.

Outlook triggers are still delayed or failing, and will stay that way until Microsoft 365 recovers. No events have been lost. Any pending Outlook events will be processed automatically once Microsoft's service is restored.

We're continuing to monitor and will post another update as the situation progresses.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: We are continuing to monitor the upstream provider outage affecting Integration Service in the United States. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in this region are still delayed. Europe, Community, Australia and India are not affected. No trigger events are lost; queued events will be processed automatically once the provider recovers.

Identified: Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in Integration Service in the United States remain delayed due to the ongoing upstream provider outage. Europe, Community, Australia and India remain recovered. No trigger events are lost; they will be processed automatically once the provider recovers.

Identified: Event triggers in Integration Service have recovered in Europe, Community, Australia and India. Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors in the United States are still delayed due to the ongoing upstream provider outage. No trigger events are lost; they will be processed automatically once the provider recovers.

Identified: The cause of delayed event triggers in Integration Service in the United States, Europe, Community, Australia and India has been identified as an upstream provider outage. Impact: Triggers for the Microsoft Outlook 365, Microsoft OneDrive & SharePoint and Microsoft Teams connectors are delayed. Triggers for other connectors may also experience some delay. No trigger events are lost; they will be processed automatically once the provider recovers.

Resolved: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining has remained stable in all regions since recovery, following the resolution of the upstream provider outage. All delayed emails have been synchronized and no emails were lost. This incident is resolved.

Monitoring: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining has recovered in all regions. We're monitoring to make sure it remains stable.

Identified: The upstream provider has largely recovered, and synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining has caught up in most regions. Email sync in the United States, Canada, Australia and Japan has been running normally since 12:06 PM UTC

As mailbox activity increases with the start of the business day in the US and Canada, sync delays could build up again in those regions while the provider is still limiting traffic. We are monitoring closely.

In Europe and Singapore, synchronization is still catching up. The backlog is decreasing slowly, so delays will continue there for now.

No emails are lost. All delayed emails will be synchronized automatically. We'll post another update when Europe and Singapore have recovered.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: Synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining remains delayed due to the ongoing upstream provider outage. We are actively monitoring the provider's recovery. No emails are lost; once the provider recovers, synchronization will resume and catch up automatically.

Identified: We are continuing to monitor the upstream provider outage that is delaying the synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining. New emails may still be delayed in appearing in Communications Mining. No emails are lost; synchronization will catch up automatically once the provider recovers.

Identified: We have identified an upstream provider outage that is delaying the synchronization of Microsoft Exchange / Outlook mailboxes into Communications Mining. Impact: New emails may be delayed in appearing in Communications Mining. No emails are lost; synchronization will catch up automatically once the provider recovers.

Resolved: The third-party provider issue that caused some Serverless jobs using Microsoft 365 activities to fail has been resolved. Microsoft 365 activities in Serverless jobs are working normally again.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.

Identified: Some Serverless jobs that use Microsoft 365 activities, such as reading a mailbox or sending an email, are failing because of an issue with a third-party provider. Affected jobs show as faulted in Orchestrator. Jobs that don't use these activities are running normally.