Limits Reference
This page documents all limits and constraints in RoleLogic. Understanding these helps you plan your automation effectively and avoid unexpected issues.
Quick Reference
Here's a summary of the most important limits:
| Category | Limit | Value |
|---|---|---|
| Rules per server (free) | Default | 2 rules |
| Conditions per rule | Maximum | 10 (1 primary + 9 AND) |
| Actions per rule | Maximum | 2 (add + remove) |
| Roles per action | Maximum | 250 roles |
| Roles per condition | Maximum | 250 roles |
| Cross-server syncs | Default | 5 linked servers |
| Cascade passes | Safety limit | 100 passes |
| API rate limit | Requests | 20 per 30 seconds |
Rule Limits
Conditions Per Rule
| Limit | Value |
|---|---|
| Primary condition | 1 (required) |
| Additional AND conditions | Up to 9 |
| Total conditions per rule | Up to 10 |
You can combine up to 10 conditions with AND logic in a single rule. This allows for precise targeting of specific member role combinations.
Actions Per Rule
| Limit | Value |
|---|---|
| Primary action | 1 (required) |
| Additional combined actions | Up to 1 |
| Total action types per rule | Up to 2 |
You can have one "Add Roles" action and one "Remove Roles" action in the same rule using the "Add Combined Action" feature.
Roles Per Condition/Action
| Limit | Value |
|---|---|
| Roles per condition | Up to 250 |
| Roles per action | Up to 250 |
You can select up to 250 roles in each condition or action. This is more than enough for virtually any server setup.
Processing Limits
Rule Evaluation Passes
| Limit | Value |
|---|---|
| Maximum evaluation passes | 100 |
When rules cascade (one rule triggers another), RoleLogic continues processing until:
- No more rules match, OR
- 100 passes have been completed
This prevents infinite loops from misconfigured rules. If your rules require more than 100 passes, consider simplifying your rule structure.
Processing Timing
| Process | Timing |
|---|---|
| Real-time processing | Triggered instantly on role changes |
| Debounce delay | 10 seconds |
| Scheduled sync interval | Every 10 minutes |
| Rule activation after update | Within 1 hour |
What these mean:
- Real-time processing: When a member's roles change, RoleLogic evaluates rules immediately
- Debounce delay: Multiple rapid role changes are batched together (10 seconds) to prevent excessive processing
- Scheduled sync: A full server sync runs every 10 minutes to catch any missed changes
- Rule activation: New or updated rules are fully active within 1 hour of saving
Rate Limiting
| Limit | Value |
|---|---|
| API requests | 20 requests per 30 seconds |
RoleLogic respects Discord's API rate limits:
- Role changes are queued and processed in order
- During high-activity periods, there may be slight delays
- The system dynamically adjusts to stay within limits
- You won't lose any changes—they're queued automatically
Quota Limits
Quotas determine how many rules and features you can use per server.
Free Plan
| Resource | Limit |
|---|---|
| Rules per server | 2 rules |
| Cross-server role slots | 5 linked servers |
| Webhook watermark | Included (shows RoleLogic branding) |
| All condition types | ✅ Full access |
| All action types | ✅ Full access |
| Testing sandbox | ✅ Full access |
| Activity log | ✅ Full access |
The free plan includes everything you need to get started. It's perfect for:
- Small servers testing RoleLogic
- Simple automation setups (verification, basic rewards)
- Servers with straightforward role hierarchies
Premium Plans
Premium plans expand your capacity:
| Resource | Premium Benefit |
|---|---|
| Rules per server | +5 to +78 additional rules (varies by tier) |
| Cross-server role slots | Expanded capacity |
| Webhook watermark | Removed for clean notifications |
| Priority support | Faster response times |
Premium Tiers (additional rules):
- Tier 1: +10 rules
- Tier 2: +26 rules
- Tier 3: +38 rules
- Tier 4: +56 rules
- Tier 5: +78 rules
Check the Upgrade page in your dashboard for current pricing and options.
Quota Allocation and Cooldowns
| Behavior | Detail |
|---|---|
| Quota assignment | Per-server allocation |
| Reassignment cooldown | 7 days |
| Unused quota | Can be reassigned after cooldown |
About the cooldown: After assigning premium quota to a server, you must wait 7 days before reassigning it to a different server. This prevents abuse and ensures service stability.
Webhook Limits
Message Content
| Limit | Value |
|---|---|
| Message length | ~2,000 characters (Discord limit) |
| Embed description | ~4,096 characters (Discord limit) |
| Total embed size | ~6,000 characters (Discord limit) |
Webhook Delivery
Webhooks are subject to Discord's rate limits:
- High-frequency events may experience slight delays
- Messages are queued and sent in order
- No messages are lost—just potentially delayed
Server and Member Limits
Servers Per Account
There's no strict limit on how many servers you can manage, but:
- Each server's rules consume quota separately
- Premium quota must be allocated to specific servers
- You can manage unlimited servers with the free tier (2 rules each)
Members Per Server
RoleLogic is built to scale with any server size:
| Server Size | Expected Performance |
|---|---|
| Small (< 1,000 members) | Instant processing |
| Medium (1,000-10,000 members) | Near-instant processing |
| Large (10,000-50,000 members) | Fast processing |
| Very large (50,000+ members) | Optimized batch processing |
For very large servers:
- Initial sync may take longer when first setting up
- Real-time processing remains fast for individual changes
- Batch operations (like rule changes affecting many members) are processed efficiently
Technical Constraints
Role Hierarchy
| Constraint | Detail |
|---|---|
| Manageable roles | Only roles below RoleLogic's role |
| Bot's own role | Cannot be modified by RoleLogic |
| Roles above bot | Cannot be assigned or removed |
This is a Discord security constraint, not a RoleLogic limitation. Learn how to configure role hierarchy →
Cross-Server Requirements
| Requirement | Detail |
|---|---|
| Bot presence | RoleLogic must be in all involved servers |
| Member presence | Member must exist in both source and target servers |
| Permissions | "Manage Roles" required in each server |
| Linked server limit | 5 servers by default |
@everyone Role
| Constraint | Detail |
|---|---|
| Presence | Every member has @everyone |
| Removability | Cannot be removed (Discord constraint) |
| Testing impact | Always include in sandbox tests |
Safety Limits
RoleLogic includes automatic safety features to prevent runaway automation.
Reverted Action Detection
If RoleLogic detects that its changes are being repeatedly undone (usually indicating a conflict with another bot or manual intervention), it will automatically stop the rule.
| Parameter | Value |
|---|---|
| Detection window | 1 hour |
| Action threshold | 100 reverted actions |
| Result | Rule automatically stopped |
When this triggers:
- The rule status changes to "Stopped"
- No further processing occurs for that rule
- You'll see a notification in your dashboard
- The Activity Log records the event
To resolve:
- Identify what's conflicting (another bot, manual changes, etc.)
- Fix the underlying conflict
- Re-enable the rule from the dashboard
Cascade Limit
| Limit | Value |
|---|---|
| Maximum passes | 100 |
| Purpose | Prevent infinite loops |
If rules trigger each other in a chain, processing stops after 100 passes. This protects your server from accidental infinite loops.
Activity Log Limits
| Limit | Value |
|---|---|
| Log entries displayed | 50 entries per page |
| Log retention | Indefinite (kept as long as server exists) |
Checking Your Limits
In the Dashboard
View your current usage:
- Open your server's dashboard
- Check the sidebar for quota information
- See "Rules: X / Y" showing current usage vs. limit
On the Upgrade Page
View detailed quota information:
- Go to the Upgrade section
- See your current plan and quota
- View all available upgrade options
- Track cooldown periods for reassignment
Planning Around Limits
Optimizing Rule Count
Consolidate where possible to maximize your quota:
Instead of 3 separate rules:
Rule 1: If Booster → add VIP
Rule 2: If Premium → add VIP
Rule 3: If Supporter → add VIP
Use 1 combined rule:
Rule 1: If has some of [Booster, Premium, Supporter] → add VIP
More tips:
- Use "Has Some Roles" with multiple roles instead of multiple rules
- Use threshold conditions ("At Least N") to consolidate counting logic
- Let rules cascade for complex multi-step automation
Managing Quota
- Delete unused or test rules promptly
- Review rules periodically and remove obsolete ones
- Consider upgrading if consistently at capacity
- Use the 7-day cooldown wisely when reallocating quota
Handling Large Servers
For servers with many members:
- Initial rule setup may take time to process all members
- Real-time processing remains fast for individual changes
- Test rules thoroughly before enabling on high-population roles
- Consider rule priority to optimize processing order
Frequently Asked Questions
What happens when I hit the rule limit?
You cannot create new rules until you free up quota. Options:
- Delete unused rules to make room
- Consolidate similar rules into one
- Upgrade to a premium plan for more quota
Existing rules continue working normally.
Can I request higher limits?
Premium plans offer expanded quotas for most users. For enterprise needs beyond the highest premium tier, contact support about custom plans.
Why is there a 7-day cooldown on quota reassignment?
The cooldown prevents abuse and ensures service stability. It encourages thoughtful allocation rather than constant switching between servers.
How do I know if I'm hitting rate limits?
You generally won't notice rate limits in normal operation. If you experience delays:
- Check if many rules are processing simultaneously
- Verify you're not in conflict with another bot
- Large batch operations may take longer during peak Discord usage
Are these limits permanent?
Limits may be adjusted over time as the service evolves. The dashboard always shows current limits, which supersede this documentation if different.
Related
- Quotas & Limits (Concepts) — Understanding the quota system
- Troubleshooting — Fix limit-related issues
- Best Practices — Optimize within limits
- Role Hierarchy — Configure permissions correctly