Description
A bot added to a guild with the bot scope while it had no working Interactions Endpoint URL (i.e., before deployment) gets stuck showing as "Offline" in the member sidebar, even after the bot is deployed, commands work correctly, and it has a hoisted role. Removing and re-adding the bot to the guild fixes the sidebar status immediately.
Since this bot uses HTTP interactions only (no gateway connection), Discord must be relying on some cached/stale presence state from the initial add rather than re-evaluating status after the endpoint becomes functional.
Steps to Reproduce
- Add bot to a guild with
bot scope in authorize URL, at a point where the bot's Interactions Endpoint URL is not yet configured / not functional and the bot has no Gateway conn.
- Configure the Interactions Endpoint URL in the Discord Developer Portal afterward, pointing to the deployed, working bot. (on CF Workers maybe)
- Verify the bot responds correctly to slash commands in the guild.
- Give the bot a role that is hoisted.
- Observe the member sidebar: bot still appears under "Offline", not under its hoisted role group.
- Kick the bot from the guild and re-add it via the same OAuth
bot scope flow.
- Observe the member sidebar again.
Expected Behavior
Bot should appear under its hoisted role group in the member sidebar as soon as it has a hoisted role and is functional, regardless of whether the Interactions Endpoint URL was configured before or after the initial guild add.
Current Behavior
Bot remains listed under "Offline" in the sidebar after being added early (before endpoint configuration), even though:
- Commands work correctly (interactions are being received and responded to).
- Bot has a hoisted role assigned.
After removing and re-adding the bot to the guild, it correctly appears under its hoisted role group instead of "Offline".
Screenshots/Videos
No response
Client and System Information
- Bot type: HTTP-only interactions bot (no gateway connection), built with Honocord on Cloudflare Workers.
- Discord info: ptb 593254 (2bac426) Host 1.0.1214 x64 (88456) Build Override: N/A Windows 11 64-bit (10.0.26200)
Description
A bot added to a guild with the
botscope while it had no working Interactions Endpoint URL (i.e., before deployment) gets stuck showing as "Offline" in the member sidebar, even after the bot is deployed, commands work correctly, and it has a hoisted role. Removing and re-adding the bot to the guild fixes the sidebar status immediately.Since this bot uses HTTP interactions only (no gateway connection), Discord must be relying on some cached/stale presence state from the initial add rather than re-evaluating status after the endpoint becomes functional.
Steps to Reproduce
botscope in authorize URL, at a point where the bot's Interactions Endpoint URL is not yet configured / not functional and the bot has no Gateway conn.botscope flow.Expected Behavior
Bot should appear under its hoisted role group in the member sidebar as soon as it has a hoisted role and is functional, regardless of whether the Interactions Endpoint URL was configured before or after the initial guild add.
Current Behavior
Bot remains listed under "Offline" in the sidebar after being added early (before endpoint configuration), even though:
After removing and re-adding the bot to the guild, it correctly appears under its hoisted role group instead of "Offline".
Screenshots/Videos
No response
Client and System Information