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
AUT - Automations
AUT - Automations
Automation workflow issues
- Automation not found or disabled
- Template configuration missing
- Workflow execution failures
RL - Rate Limiting
RL - Rate Limiting
Rate limiting and performance issues
- Token buckets empty
- Action caps exceeded
- Queue overflow
PERM - Permissions
PERM - Permissions
Discord permission problems
- Bot missing required permissions
- User lacking access rights
- Role hierarchy issues
EXT - External Services
EXT - External Services
External API and service issues
- Discord API rate limits
- Webhook failures
- Network timeouts
SYS - System
SYS - System
Platform and infrastructure problems
- Bot instance crashes
- Database connection issues
- Resource exhaustion
DB - Database
DB - Database
Data storage and conflicts
- Write conflicts
- Connection failures
- Data corruption
Common Error Codes
Authentication & Authorization (1xxx)
| Code | Message | Remediation |
|---|---|---|
| 1401 | Sign in required | Sign in to Discord |
| 1403 | You don’t have access here | Switch account or ask admin |
| 1404 | Your session has expired | Sign in again |
Permissions (2xxx)
| Code | Message | Remediation |
|---|---|---|
| PERM-2201 | Bot missing required permission | Open “Fix Permissions” |
| PERM-2202 | You lack required server permissions | Ask admin for permissions |
| PERM-2210 | Bot isn’t in this server | Invite bot to server |
Resources (3xxx)
| Code | Message | Remediation |
|---|---|---|
| AUT-3301 | Automation doesn’t exist | Refresh automation list |
| AUT-3302 | Automation is paused | Enable automation |
| AUT-3305 | Required inputs not set | Complete configuration |
Rate Limits (4xxx)
| Code | Message | Remediation |
|---|---|---|
| RL-4101 | Rate limit: server actions per minute | Wait or adjust limits |
| RL-4102 | Rate limit: action cap reached | Wait or increase cap |
| RL-4103 | Automation queue is full | Reduce load or wait |
| RL-4104 | Rate limit: too many messages sent | Wait for message bucket refill |
Platform & External (5xxx)
| Code | Message | Remediation |
|---|---|---|
| EXT-5101 | Discord API rate limited | Wait automatically or retry later |
| SYS-5401 | Bot instance crashed | Restart bot instance |
| SYS-5404 | Automation took too long | Optimize workflow |
Error Display in Dashboard
Toast Notifications
Errors appear as toast notifications with this format: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: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
- Which Discord permission is missing
- What action was attempted
- Current bot permissions vs. required
- Quick fix suggestions
- Which automation failed
- What step in the workflow
- Configuration issues
- Variable or input problems
Resolving Common Errors
Rate Limiting Issues
RL-4101: Guild Minute Limit
RL-4101: Guild Minute Limit
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
RL-4102: Action Cap Reached
RL-4102: Action Cap Reached
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
RL-4103: Queue Full
RL-4103: Queue Full
Problem: Too many automations waiting to executeQuick Fixes:
- Wait for queue to process current items
- Check if any automations are stuck
Permission Issues
PERM-2201: Bot Missing Permission
PERM-2201: Bot Missing Permission
Problem: Bot lacks required Discord permissionQuick Fix: Use the “Fix Permissions” button in the dashboardManual Fix:
- Go to Discord Server Settings → Roles
- Find the Automater bot role
- Grant the missing permission shown in the error
- Verify bot role is above roles it needs to manage
PERM-2210: Bot Not in Server
PERM-2210: Bot Not in Server
Problem: Bot was removed or never invitedFix: Re-invite the bot with proper permissions
- Use the dashboard invite link
- Select the correct server
- Grant all recommended permissions
Automation Issues
AUT-3301: Automation Not Found
AUT-3301: Automation Not Found
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
AUT-3305: Required Inputs Missing
AUT-3305: Required Inputs Missing
Problem: Template or pack missing required configurationFix: Complete the automation configuration
- Go to automation settings
- Fill in all required fields (marked with *)
- 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.
Next Steps
- Activity Feed - Monitor errors in real-time
- Troubleshooting Guide - Step-by-step problem solving
- Rate Limiting - Understand and prevent rate limit errors
- Server Overview - Check permissions and system health