Skip to content
🎉 Launch sale:50% off everything over $22 — automatically applied at checkout· ends Aug 2Shop the sale →
DevOps AI ToolKit
Newsletter
All guides
AI for Slack By James Joyner IV · · 8 min read Last reviewed Jul 2026

Slack Error: 'ura_max_channels' — Cause, Fix, and Troubleshooting Guide

Quick answer

Fix the Slack ura_max_channels error: a single-channel guest is already at their channel limit. Convert them to a multi-channel guest or member to invite them.

  • #slack
  • #api
  • #troubleshooting
  • #errors
Free toolkit

Stuck on this Slack error? Get the free incident triage checklist

A one-page PDF — the exact steps to isolate, fix, and verify a production error like this one. No spam, unsubscribe anytime.

Overview

ura_max_channels is returned by conversations.invite when the invited user is a single-channel guest (“ultra restricted access”, hence ura) who is already in the maximum number of conversations their account type allows. By definition a single-channel guest belongs to one channel; inviting them to another exceeds that.

{
    "ok": false,
    "error": "ura_max_channels"
}

Symptoms

  • Inviting a specific external/guest user fails while inviting regular members succeeds.
  • The user is a restricted guest account, not a full member.
  • The error is user-specific, not channel- or scope-specific.

Common Root Causes

1. Inviting a single-channel guest to a second channel

Single-channel guests are capped at one channel; a second invite trips the limit.

2. Guest already at their allotted channel count

An ultra-restricted account is at its maximum and cannot be added to more.

3. Bulk invite includes guest accounts

An automation invites a mixed roster that contains single-channel guests without accounting for their limits.

How to diagnose

Check the account type via users.info:

curl -s "https://slack.com/api/users.info?user=U0GUEST001" \
  -H "Authorization: Bearer $SLACK_BOT_TOKEN"
{"ok": true, "user": {"id": "U0GUEST001", "is_ultra_restricted": true, "is_restricted": true}}

is_ultra_restricted: true marks a single-channel guest — the source of ura_max_channels.

Fixes

  • Convert the account type: an admin can change a single-channel guest to a multi-channel guest (or full member) so they can join additional channels.
  • Don’t invite single-channel guests to extra channels — respect the one-channel constraint in your automation.
  • Filter rosters: skip is_ultra_restricted users in bulk-invite flows, or handle them separately.

What to watch out for

  • This is an account-type policy, not a bug — the fix usually lives with a workspace admin, not in code.
  • is_ultra_restricted (single-channel guest) vs is_restricted (multi-channel guest): only the former is capped at one channel.
  • For external collaboration across channels, Slack Connect shared channels are often the better model than guest accounts.
Free download · 368-page PDF

Fixed it? Get 500 Slack & DevOps AI prompts — free

500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.

  • 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
  • Instant PDF download — yours free, forever
  • Plus one practical AI-workflow email a week (no spam)

Single opt-in · unsubscribe anytime · no spam.

Did this fix your issue?

Free download · 368-page PDF

Get 500 Battle-Tested DevOps AI Prompts — Free

500 battle-tested, copy-paste AI prompts engineered by a senior systems engineer — every one with fill-in placeholders and safety/back-out notes. Drop your email and it's yours.

  • 500 prompts: Linux · Kubernetes · Terraform · OpenStack · GitLab · Docker · Monitoring · Incident Response
  • Instant PDF download — yours free, forever
  • Plus one practical AI-workflow email a week (no spam)

Single opt-in · unsubscribe anytime · no spam.