Discord error 30034: Maximum number of daily application command creates reached (200)
Last verified against Discord Developer Docs - Opcodes and status codes
Maximum number of daily application command creates has been reached (200)What error 30034 means
Your application has created more than 200 application commands in the last day for a guild, and further creates are blocked until the daily window rolls over. Discord counts creates, and a bulk overwrite (PUT) that replaces commands counts each newly-created command. A deploy script that wipes and re-registers 30 commands on every restart burns through 200 in seven restarts.
The trap is running command registration on process start. It is convenient, it is in every tutorial, and it is what exhausts this limit during a day of active development with frequent restarts. Guild commands update instantly, which makes them attractive for dev servers, but they count against this same daily cap.
What it looks like
{
"message": "Maximum number of daily application command creates has been reached (200)",
"code": 30034
}Why it happens
- Command registration runs on every bot startup
- Development loop with many restarts, each re-creating commands
- Multiple instances or CI jobs registering commands against the same guild
- Registering the same command set to many guilds in a loop
How to fix Discord error 30034
- 1Stop registering commands at startup; move it to a separate deploy script you run only when commands change
- 2Wait for the daily window to reset (the response may include retry_after) and then deploy once
- 3Diff your desired command list against GET /applications/{id}/guilds/{guild.id}/commands and only create or edit what changed
- 4Use global commands for production and a single dev guild for testing to minimize creates
How to stop it recurring
Treat command registration like a database migration: explicit, versioned, run by a human or by CI when the definition file changes, never as a side effect of booting the bot. A hash of the command definitions stored next to the bot lets you skip the PUT when nothing has changed.
The daily create budget is generous for deployment and hostile to startup-time registration, which is the point. Command quotas, name rules and this budget are on the Discord limits page; if your deploy also edits stale command IDs, pair this fix with 10063 handling so a re-registration does not cascade into a second failure.
Official reference: Discord Developer Docs - Opcodes and status codes. See all Discord error codes or the Discord limits and quotas.
Related codes
Error 30034 - quick answers
What does Discord error 30034 mean?
Your application has created more than 200 application commands in the last day for a guild, and further creates are blocked until the daily window rolls over. Discord counts creates , and a bulk overwrite (PUT) that replaces commands counts each newly-created command. A deploy script that wipes and re-registers 30 commands on every restart burns through 200 in seven restarts.
How do I fix Discord error 30034?
1. Stop registering commands at startup; move it to a separate deploy script you run only when commands change 2. Wait for the daily window to reset (the response may include retry_after) and then deploy once 3. Diff your desired command list against GET /applications/{id}/guilds/{guild.id}/commands and only create or edit what changed 4. Use global commands for production and a single dev guild for testing to minimize creates
Can I retry after error 30034?
Yes - this is a retryable condition. Back off (start around one second and double on each attempt, with jitter) and watch for a retry-after hint from the platform before resending.
Stop debugging Discord by hand
Connect the channel through Conferbot: tokens, webhooks and retries are handled, failures show as readable status.