Skip to main content
Slack

Trouble with Gmail add-on Integration

Degraded Lasted 10h 3m · started · Slack's page

Level
confirmed
Worst impact
Degraded
Components
Apps/Integrations/APIs
Down Index
47of 100

What to do

  • Check whether you use Slack Apps/Integrations/APIs. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 10h 3m it lasted.

    Anything that failed between 2026-06-10 20:36 UTC and 2026-06-11 06:39 UTC may need a replay.
  • Subscribe to Slack's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=slack works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from Slack 8

  1. update

    We're aware of an issue impacting the Slack Gmail add-on integration. As a result, users are unable to interact with the add-on and may encounter a “Something went wrong when executing the add-on. For help, contact the add-on developer” error message when attempting to use it. We are investigating the cause of this issue. We'll provide an update in 30 minutes or sooner if additional information becomes available.

    provider

  2. update

    We’re still actively investigating the issue impacting the Slack Gmail add-on. We are working to identify the cause, and no workaround is currently available. We’ll provide an update in 30 minutes or sooner if additional information becomes available.

    provider

  3. update

    We’re still investigating the issue impacting Slack Gmail add-ons. No additional news to share just yet, but we’re focused on getting things back to normal as quickly as we can. We apologize for the continued trouble. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

    provider

  4. update

    We’re still investigating the issue impacting Slack Gmail add-ons. No additional news to share just yet, but we’re focused on getting things back to normal as quickly as we can. We apologize for the continued trouble. We’ll provide an update in 60 minutes or sooner if additional information becomes available.

    provider

  5. update

    We continue to investigate the issue impacting Slack Gmail add-ons. We've identified the cause and our teams are working on a fix to resolve the issue as soon as possible. We’ll provide an update once additional information becomes available.

    provider

  6. update

    We’re actively working on the fix to resolve the issue. We estimate this will take approximately four hours or more to complete, and validate the fix, before it can be deployed. As such, the next status update will be once the fix has been completed and validated, or we have new information to share. We apologize for any inconvenience this issue is causing for users.

    provider

  7. update

    We’re continuing to investigate the issues with the Slack Gmail add-on and are actively working on a fix to resolve the issue. There’s no new information to share at this time, but we’ll provide an update as soon as we have more details on implementing the fix. We apologize for any inconvenience this issue is causing for users.

    provider

  8. update

    We've resolved the issue that prevented customers from using the Slack Gmail add-on. The fix has been successfully deployed; health metrics have stabilized, and the Gmail add-on is now fully operational for all affected users. We apologize for any inconvenience this may have caused.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-f84c3503aa

Is Slack still down?

No, this incident was resolved 2026-06-11 06:39 UTC. For Slack's live state, see https://down.guide/slack.

How long did it last?

10h 3m, from 2026-06-10 20:36 UTC to 2026-06-11 06:39 UTC, by the times Slack posted.

What was affected?

Slack named Apps/Integrations/APIs.

What caused it?

Slack hasn't published a root cause. If it does, it shows here.

Where does this come from?

Slack's official status page, https://slack-status.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.