Problem
Understand delayed Discord actions caused by rate limiting.
Start at The affected feature and its Action Log.
Common causes
- Too many Discord actions were requested in a short period.
- A bulk restore, publish, or notification job is intentionally rate-limited.
- Repeated manual retries keep the same queue busy.
Checks
- 1
Look for a queued, retrying, or delayed status rather than an immediate failure.
- 2
Check whether a restore or background job shows progress.
- 3
Confirm the target channel and permissions before retrying.
Fix
- 1
Let the queued job continue and avoid repeated clicks.
- 2
Use the page's Refresh action to inspect progress.
- 3
Retry only after a terminal failure and after correcting its reported cause.