Orphaned Guild Slash Commands Persist After Application Change

[12jesedi]

Description

I am experiencing persistent duplicate guild-scoped slash commands that cannot be removed via the API.

In a specific server, multiple slash commands appear duplicated. Each duplicate shows a different command ID. Only one set belongs to my active application.

The additional command IDs do not correspond to any existing application in the Developer Portal.

Clearing global commands, clearing guild commands, and forcing guild sync via the API does not remove the duplicates.

These appear to be orphaned guild-scoped application command records that are no longer owned by an active application.

Server ID: 1423821092136554656

Active Application ID: 1459337302089273457

Example duplicate command name: /gamble_audit (and others)

Orphan Command ID: 1477527904186404866

Steps to Reproduce

1. Register guild-scoped slash commands via the API.
2. Refactor or materially change command registration (e.g., moving command definitions).
3. Sync commands again using the API.
4. Observe duplicate slash commands in the guild.
5. Attempt to clear commands using:
   • tree.clear_commands(guild=...)
   • tree.clear_commands(guild=None)
   • tree.sync(guild=...)
   • tree.sync()
6. Observe that duplicate commands persist.

Expected Behavior

Clearing and re-syncing guild commands via the API should remove any outdated or orphaned slash command records.

Only the commands owned by the currently active application should remain visible in the guild.

Current Behavior

Duplicate slash commands persist in the guild.

Each duplicate shows a different command ID.

One command ID belongs to the active application. The other command ID does not correspond to any existing application in the Developer Portal.

The orphaned commands cannot be removed through any available API methods.

Screenshots/Videos

Client and System Information

discord.py (latest stable)
Python 3.12
Commands registered via application command API
Tested on Windows 11 and browser client

[infinitestory]

I suspect the "orphaned" command is in fact a global (i.e. non-guild-registered) command. If not, can you share a minimal code example that repros from a freshly created app?

[12jesedi]

The duplicate commands appear only in the guild and not in DMs.

I have:

• Cleared global commands via tree.clear_commands(guild=None) and synced.
• Cleared guild commands via tree.clear_commands(guild=guild) and synced.
• Forced a guild sync followed by a global sync.
• Verified only one active application exists in the Developer Portal.
• Verified that one of the duplicate command IDs does not correspond to any existing application.

After clearing globals, the duplicates remain visible in the guild.
After clearing guild commands, the duplicates remain visible in the guild.
DMs only show a single command.

This suggests the extra command record is not owned by the currently active application and is not removable via the API.

If needed, I can provide a minimal repo but this issue is occurring in an existing production server where commands were previously registered and later refactored.