Slack “Redirect Circle” when switching between Workspaces

The Slack “Redirect Circle” error occurs when switching between multiple workspaces because conflicting browser authentication cookies, cached OAuth session tokens, or broken URL protocol handlers fail to hand off authorization parameters between your web browser and the desktop client. This loop continuously redirects your browser through login URLs without opening the target workspace, interrupting workflow across desktop and mobile environments. Resolving this issue requires clearing browser session cookies, resetting desktop protocol links, or signing out of all workspaces simultaneously to clear token collisions.

Fast-Fix: The 45-Second Solution

A Slack redirect circle when switching between workspaces occurs when conflicting OAuth session cookies or corrupted local protocol handler tokens endlessly bounce the authentication request between your browser and the desktop app. To fix this immediately, sign out of all active workspaces at [slack.com/signout](<https://slack.com/signout>), clear your default browser’s cookies, and reopen Slack directly from the desktop client.

Quick Logic Snapshot

• Severity: High (blocks navigation between corporate workspaces and delays access to channels and messages).
• Impact: Users maintaining active accounts across multiple Slack orgs, Enterprise Grid instances, or guest workspaces.
• Primary Cause: Conflicting OAuth 2.0 session cookies in the default web browser colliding with cached workspace identity tokens in the desktop app.
• Secondary/Security Cause: Misconfigured custom URL protocol handlers (slack://) failing to pass token parameters back from single sign-on (SSO) redirects.

Low Risk vs. High Risk Scenarios

• Low Risk (Browser Session Contamination): If the redirect loop only happens when clicking workspace switcher links inside a browser tab, the issue is isolated to cached web cookies. Signing out of slack.com in your browser resolves the loop.
• Moderate Risk (Desktop Deep-Link Failure): If the browser opens and redirects endlessly when attempting to open the desktop app from the workspace switcher, the OS protocol handler for slack:// links is broken or blocked by browser security settings.
• High Risk (Enterprise Grid Token Revocation / Identity Loop): If switching workspaces triggers an endless authentication cycle alongside SSO identity provider warnings, your account UPN or SAML token has expired or encountered a tenant policy mismatch.

What This Means

Think of workspace switching like passing through a security turnstile with an electronic passcard. Your browser acts as the card scanner, while the Slack desktop app is the gate itself.

When you click to switch from Workspace A to Workspace B, Slack sends an authentication request to your default browser to verify your badge for Workspace B. The browser checks its cached cookies, generates a temporary authorization token, and sends a deep-link command (slack://workspace-b) back to open the desktop app.

A redirect circle happens when the browser holds a lingering cookie from Workspace A or a secondary SSO account. The scanner reads the passcard for Workspace A, sees that it doesn’t match Workspace B’s portal, and bounces you back to the login page. When you click log in, the browser reads the same cached passcard and bounces you again, creating an endless loop where neither the browser nor the app can finish the handshake.

Logic Escalators

• Using Multiple Browser Profiles Without Container Isolation: Switching workspaces in a browser window where personal and corporate Google or Microsoft accounts are active simultaneously.
• VPN Split-Tunneling and Security Proxies: Network gateways stripping HTTP header referrer policies or delaying authorization responses during workspace handshakes.
• Third-Party Cookie Restrictions Enabled: Browsers like Safari, Brave, or Chrome blocking cross-site storage access needed for multi-workspace OAuth redirects.

Confused With / False Positives

• Slack Enterprise Grid SSO Login Failures: SSO failures prevent logging into an organization entirely with explicit SAML error codes, whereas a redirect circle endlessly loops between valid workspace URLs. See Troubleshooting: Slack Enterprise Grid SSO Login Failures.
• “You Don’t Have Permission to Access This Workspace” Loop: Access permission loops display explicit authorization rejection pages rather than continuously refreshing the browser URL bar. See Troubleshooting: “You don’t have permission to access this workspace” Loop.
• Script Error During OAuth Authentication: Script errors present explicit JavaScript dialog popups during token exchange rather than smooth URL redirection cycles. See Slack “Script Error” during OAuth Authentication.
• Modern Auth Prompt Loops (ADAL/MSAL): Modern auth loops continuously re-prompt for corporate credentials inside an Azure AD/Entra ID window rather than bouncing between Slack workspace domains. See Fix: Slack “Modern Auth” Prompt Loops (ADAL/MSAL).

What To Do Right Now

1. Sign Out of All Workspaces via Web: Open your browser and go to [slack.com/signout](<https://slack.com/signout>). This forcefully terminates all cached web session cookies across all connected workspaces.
2. Clear Browser Cookies for Slack: In your default browser settings, search for site data for slack.com and clear all associated cookies and site storage.
3. Reset Default Application Protocol Handler: When prompted by your browser with “Open Slack?”, check the box for “Always allow slack.com to open links of this type” and click Open.
4. Clear Slack Desktop App Cache: Open the Slack desktop client, navigate to Help > Troubleshooting > Clear Cache and Restart to flush stored desktop tokens. For a thorough cleanup, refer to How to Clear Slack Desktop Cache (The Deep Clean Method).

Immediate Intervention Flags

• Browser address bar cycling rapidly through dozens of URL redirects per second, causing high system resource consumption.
• Explicit browser security warnings blocking slack:// protocol execution due to modified registry or default app settings.
• Identity provider sign-in pages repeatedly requesting multi-factor authentication without advancing to Slack.

What a SysAdmin Will Check

1. Inspect SAML and OAuth Session Logs: Review the identity provider and Slack Enterprise Grid audit logs to confirm whether authorization codes (code=) are successfully issued and redeemed.
2. Verify Identity Provider Attribute Alignment: Check that the user’s immutable NameID or email matches across all workspaces within the Enterprise Grid structure. See Troubleshooting: Slack Enterprise “Identity Provider” Mismatch.
3. Verify OS Protocol Handler Associations: Ensure slack:// deep-links are correctly associated with %LocalAppData%\slack\slack.exe in Windows Default Apps or macOS URL scheme bindings.
4. Check Browser Cross-Site Tracking Policies: Verify that Enterprise Endpoint Management policies are not forcing strict third-party cookie blocks on .slack.com domains.

Operations Summary

A Slack “Redirect Circle” when switching between workspaces is fundamentally a token handoff failure between your browser’s active session state and the desktop app’s internal URL protocol handler. By signing out of all active web sessions, clearing browser cookies for slack.com, and resetting local app cache, you remove the conflicting session parameters that trigger the loop. If the issue continues across multiple browser profiles, verifying OS default protocol associations or having an administrator re-synchronize Enterprise Grid SSO sessions ensures seamless switching across all your organization’s workspaces.