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 · · 7 min read Last reviewed Jul 2026

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

Quick answer

Fix the Slack too_many_users error: conversations.open exceeded the multi-person DM participant limit. Cap the group DM or use a channel instead.

  • #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

too_many_users is returned by conversations.open when you try to open a multi-person DM (MPIM) with more participants than Slack allows. Group DMs are capped; past that ceiling you must use a channel.

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

Symptoms

  • Small group DMs open fine; a larger participant list fails.
  • The failure scales with the number of users you pass.
  • Only affects MPIM opens, not channel posts.

Common Root Causes

1. MPIM participant cap exceeded

Group DMs support a limited number of people; adding more than the maximum returns too_many_users.

2. Fanning out an alert to a big user list as a group DM

Trying to DM a large on-call rotation as one MPIM instead of using a channel.

3. Accumulated/duplicated ids inflating the count

A list with duplicates or extra ids pushes the effective count over the limit.

How to diagnose

Count the distinct users you’re sending:

echo "U0USER0001,U0USER0002,...,U0USER0009" | tr ',' '\n' | sort -u | wc -l
9

Then reproduce the open with the oversized list:

curl -s -X POST https://slack.com/api/conversations.open \
  -H "Authorization: Bearer $SLACK_BOT_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"users":"U0USER0001,U0USER0002,U0USER0003,U0USER0004,U0USER0005,U0USER0006,U0USER0007,U0USER0008,U0USER0009"}'
{"ok": false, "error": "too_many_users"}

Fixes

  • Use a channel for anything beyond a small group — create/post to a private channel and invite the members instead of a giant MPIM.
  • Cap the participant list to the MPIM limit; dedupe ids before counting.
  • Split large audiences into multiple smaller DMs only if a channel truly isn’t appropriate.

What to watch out for

  • too_many_users (over the MPIM cap) is the mirror of not_enough_users (below the minimum); both are about the participant count.
  • Deduplicate ids first — duplicates count toward the limit and cause avoidable failures.
  • Group DMs aren’t a scalable broadcast mechanism; for on-call fan-out, a dedicated channel with @here/user-group mentions scales better.
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.