Skip to main content

Error Code Overview

Automater uses a structured error code system that provides clear, actionable information when things go wrong. Instead of cryptic error messages, you get organized error families with specific remediation steps.

Error Families

6 organized families: AUT (Automation), RL (Rate Limiting), PERM (Permissions), EXT (External), SYS (System), DB (Database)

Actionable Messages

Each error includes clear description and specific steps to resolve the issue

Activity Integration

Errors appear in your activity feed with retry buttons and documentation links

Smart Troubleshooting

Automated diagnosis and fix suggestions based on error context

Error Code Format

Display Format

User-facing: {FAMILY}-{4-DIGIT}
  • Examples: AUT-4101, RL-4102, PERM-2201

Error Families

Automation workflow issues
  • Automation not found or disabled
  • Template configuration missing
  • Workflow execution failures
Rate limiting and performance issues
  • Token buckets empty
  • Action caps exceeded
  • Queue overflow
Discord permission problems
  • Bot missing required permissions
  • User lacking access rights
  • Role hierarchy issues
External API and service issues
  • Discord API rate limits
  • Webhook failures
  • Network timeouts
Platform and infrastructure problems
  • Bot instance crashes
  • Database connection issues
  • Resource exhaustion
Data storage and conflicts
  • Write conflicts
  • Connection failures
  • Data corruption

Common Error Codes

Authentication & Authorization (1xxx)

CodeMessageRemediation
1401Sign in requiredSign in to Discord
1403You don’t have access hereSwitch account or ask admin
1404Your session has expiredSign in again

Permissions (2xxx)

CodeMessageRemediation
PERM-2201Bot missing required permissionOpen “Fix Permissions”
PERM-2202You lack required server permissionsAsk admin for permissions
PERM-2210Bot isn’t in this serverInvite bot to server

Resources (3xxx)

CodeMessageRemediation
AUT-3301Automation doesn’t existRefresh automation list
AUT-3302Automation is pausedEnable automation
AUT-3305Required inputs not setComplete configuration

Rate Limits (4xxx)

CodeMessageRemediation
RL-4101Rate limit: server actions per minuteWait or adjust limits
RL-4102Rate limit: action cap reachedWait or increase cap
RL-4103Automation queue is fullReduce load or wait
RL-4104Rate limit: too many messages sentWait for message bucket refill

Platform & External (5xxx)

CodeMessageRemediation
EXT-5101Discord API rate limitedWait automatically or retry later
SYS-5401Bot instance crashedRestart bot instance
SYS-5404Automation took too longOptimize workflow

Error Display in Dashboard

Toast Notifications

Errors appear as toast notifications with this format:
RL-4101 · Rate limit (server/min). Wait a few seconds. [View Limits]
PERM-2201 · Bot missing Manage Roles permission. [Fix Permissions]
AUT-3301 · Automation 'Welcome Bot' not found. [Refresh List]

Activity Feed Integration

Errors in the activity feed include:
  • Error Code: Clickable error code with documentation link
  • Context: What triggered the error
  • Timestamp: When the error occurred
  • Actions: Retry, fix, or configure buttons
  • Status: Resolved/unresolved indicator

Error Cards

Detailed error displays show:
🔴 AUT-4102 · Action cap reached
   "Too many role assignments in the last minute"
   → [Edit Rate Limits] [Documentation]

🟡 RL-4201 · User cooldown active
   "Command cooldown active for @username"
   → [View Cooldowns] [Skip Once]

Error Context & Details

What Error Context Includes

Each error provides specific context about what went wrong: Rate Limiting Errors (RL-4xxx):
  • Which bucket is empty (guild, user, flow, action-type)
  • Tokens needed vs. available
  • Estimated time until refill (ETA)
  • Which automation triggered the limit
Permission Errors (PERM-2xxx):
  • Which Discord permission is missing
  • What action was attempted
  • Current bot permissions vs. required
  • Quick fix suggestions
Automation Errors (AUT-3xxx):
  • Which automation failed
  • What step in the workflow
  • Configuration issues
  • Variable or input problems

Resolving Common Errors

Rate Limiting Issues

Problem: Too many server actions in the last minuteQuick Fixes:
  • Wait 10-30 seconds for token refill
  • Check which automations are most active
  • Consider raising guild minute capacity
Long-term: Optimize high-frequency automations
Problem: Too many of a specific action type (messages, roles, etc.)Quick Fixes:
  • Wait for the specific action bucket to refill
  • Check action-specific limits in rate limiting settings
Long-term: Increase action type limits or optimize workflows
Problem: Too many automations waiting to executeQuick Fixes:
  • Wait for queue to process current items
  • Check if any automations are stuck
Long-term: Increase concurrency limits or optimize slow automations

Permission Issues

Problem: Bot lacks required Discord permissionQuick Fix: Use the “Fix Permissions” button in the dashboardManual Fix:
  1. Go to Discord Server Settings → Roles
  2. Find the Automater bot role
  3. Grant the missing permission shown in the error
  4. Verify bot role is above roles it needs to manage
Problem: Bot was removed or never invitedFix: Re-invite the bot with proper permissions
  1. Use the dashboard invite link
  2. Select the correct server
  3. Grant all recommended permissions

Automation Issues

Problem: Automation was deleted or ID changedQuick Fixes:
  • Refresh the automation list
  • Check if automation was accidentally deleted
  • Verify you’re looking at the correct server
Problem: Template or pack missing required configurationFix: Complete the automation configuration
  1. Go to automation settings
  2. Fill in all required fields (marked with *)
  3. Save the configuration

Error Prevention

Best Practices

  • Monitor Rate Limits: Check dashboard metrics regularly
  • Test Changes: Use test automations before deploying
  • Verify Permissions: Use permission checker before creating automations
  • Configure Properly: Complete all required settings during setup

Proactive Monitoring

The dashboard helps prevent errors by showing:
  • Rate limit usage: Before hitting limits
  • Permission status: Missing permissions highlighted
  • Configuration warnings: Incomplete setups flagged
  • Performance alerts: Slow or failing automations identified
Most errors are automatically retryable. The system will attempt to retry failed actions with exponential backoff when appropriate.
Critical errors (5xxx codes) may require manual intervention or indicate platform issues. Check system status and contact support if persistent.

Next Steps