Crash when queue empties or all listeners leave voice

[tinongskie]

The bot crashes when there is no music left to play or all members of the Discord call have left the call

[shiftybitshiftr]

I do not see enough detail yet to tell whether this is a Muse bug or a runtime/container crash. Could you paste the full logs/stack trace around the crash, preferably with DEBUG=* enabled?

[shiftybitshiftr]

I think I found a real issue for one specific part of this report: when the queue naturally empties and /config set-auto-announce-next-song is enabled, Muse can try to send an empty auto-announce message after advancing past the final track.

I opened a draft fix in #1316. The PR snapshot image is now published here:

ghcr.io/museofficial/muse:pr-1316

If you are using Docker Compose, you can test it by temporarily replacing your Muse image with that tag, then running:

docker compose pull
docker compose up -d

Can you confirm whether auto-announce is enabled on the server where this happens, and whether the PR image fixes the crash when the queue naturally empties?

The separate case where all users leave the voice channel does not appear to be the same issue from the code path I checked. That path should just disconnect the bot. If you are still seeing an actual process crash when users leave, please include the logs/stack trace for that specific case so we can investigate it separately.

[tinongskie]

this is the log… 2026-05-14 19:55:06.582310+08:00======================================== 2026-05-14 19:55:06.582375+08:00======================================== 2026-05-14 19:55:06.582385+08:00================= muse ================= 2026-05-14 19:55:06.582394+08:00======================================== 2026-05-14 19:55:06.582402+08:00=========== Made with 🎶 by ============ 2026-05-14 19:55:06.582416+08:00==== https://github.com/codetheweb ===== 2026-05-14 19:55:06.582424+08:00======================================== 2026-05-14 19:55:06.582432+08:00======================================== 2026-05-14 19:55:06.582440+08:002026-05-14T11:55:06.582440181Z 2026-05-14 19:55:06.582447+08:00Running version 2.11.4 built on 4/26/2026 (commit 7837f4f) 2026-05-14 19:55:06.582459+08:002026-05-14T11:55:06.582459399Z 2026-05-14 19:55:06.582467+08:00🔧 Need help? https://github.com/codetheweb/muse/discussions/new 2026-05-14 19:55:06.582479+08:00🐛 Bug? https://github.com/codetheweb/muse/issues/new 2026-05-14 19:55:06.582487+08:00✨ New feature? https://github.com/codetheweb/muse/issues/new 2026-05-14 19:55:06.582506+08:00☕ Discussion? https://github.com/codetheweb/muse/discussions/new 2026-05-14 19:55:06.582515+08:00💰 Help me? https://www.paypal.me/codetheweb https://github.com/sponsors/codetheweb 2026-05-14 19:55:06.582559+08:002026-05-14T11:55:06.582559349Z 2026-05-14 19:55:06.582582+08:002026-05-14T11:55:06.582582116Z 2026-05-14 19:55:06.586232+08:00- Applying database migrations... 2026-05-14 19:55:07.234651+08:00✔ Database migrations applied. 2026-05-14 19:55:07.510538+08:00YT_DLP_VERSION=2026.03.17 (/opt/yt-dlp/bin/yt-dlp) 2026-05-14 19:55:07.543683+08:00- 📡 connecting to Discord... 2026-05-14 19:55:10.553002+08:00✔ Ready! Invite the bot with https://discordapp.com/oauth2/authorize?client_id=1498264779293200394&scope=bot%20applications.commands&permissions=36700160 2026-05-15 ***@***.***/rest/src/lib/handlers/Shared.ts:152 2026-05-15 13:48:11.520824+08:00throw new DiscordAPIError(data, 'code' in data ? data.code : data.error, status, method, url, requestData); 2026-05-15 13:48:11.520854+08:00^ 2026-05-15 13:48:11.520885+08:002026-05-15T05:48:11.520885552Z 2026-05-15 13:48:11.520908+08:00DiscordAPIError[50006]: Cannot send an empty message 2026-05-15 13:48:11.520917+08:00at handleErrors ***@***.***/rest/src/lib/handlers/Shared.ts:152:10) 2026-05-15 13:48:11.520926+08:00at process.processTicksAndRejections (node:internal/process/task_queues:103:5) 2026-05-15 13:48:11.520940+08:00at async SequentialHandler.runRequest ***@***.***/rest/src/lib/handlers/SequentialHandler.ts:399:20) 2026-05-15 13:48:11.520949+08:00at async SequentialHandler.queueRequest ***@***.***/rest/src/lib/handlers/SequentialHandler.ts:169:11) 2026-05-15 13:48:11.520963+08:00at async REST.request ***@***.***/rest/src/lib/REST.ts:343:20) 2026-05-15 13:48:11.520973+08:00at async VoiceChannel.send (/usr/app/node_modules/discord.js/src/structures/interfaces/TextBasedChannel.js:162:15) 2026-05-15 13:48:11.520981+08:00at async default.onAudioPlayerIdle (/usr/app/src/services/player.ts:670:9) { 2026-05-15 13:48:11.520995+08:00requestBody: { 2026-05-15 13:48:11.521004+08:00files: [], 2026-05-15 13:48:11.521013+08:00json: { 2026-05-15 13:48:11.521021+08:00content: undefined, 2026-05-15 13:48:11.521030+08:00tts: false, 2026-05-15 13:48:11.521038+08:00nonce: undefined, 2026-05-15 13:48:11.521051+08:00embeds: [], 2026-05-15 13:48:11.521071+08:00components: undefined, 2026-05-15 13:48:11.521085+08:00username: undefined, 2026-05-15 13:48:11.521100+08:00avatar_url: undefined, 2026-05-15 13:48:11.521115+08:00allowed_mentions: undefined, 2026-05-15 13:48:11.521137+08:00flags: undefined, 2026-05-15 13:48:11.521153+08:00message_reference: undefined, 2026-05-15 13:48:11.521168+08:00attachments: undefined, 2026-05-15 13:48:11.521187+08:00sticker_ids: undefined, 2026-05-15 13:48:11.521196+08:00thread_name: undefined 2026-05-15 13:48:11.521209+08:00} 2026-05-15 13:48:11.521218+08:00}, 2026-05-15 13:48:11.521226+08:00rawError: { message: 'Cannot send an empty message', code: 50006 }, 2026-05-15 13:48:11.521236+08:00code: 50006, 2026-05-15 13:48:11.521244+08:00status: 400, 2026-05-15 13:48:11.521253+08:00method: 'POST', 2026-05-15 13:48:11.521266+08:00url: ' https://discord.com/api/v10/channels/1483039018366271618/messages' 2026-05-15 13:48:11.521275+08:00} 2026-05-15 13:48:11.521284+08:002026-05-15T05:48:11.521284069Z 2026-05-15 13:48:11.521292+08:00Node.js v22.22.2

…

On Mon, May 4, 2026 at 12:19 PM Michael ***@***.***> wrote: *shiftybitshiftr* left a comment (museofficial/muse#1314) <#1314 (comment)> I think I found a real issue for one specific part of this report: when the queue naturally empties and /config set-auto-announce-next-song is enabled, Muse can try to send an empty auto-announce message after advancing past the final track. Can you confirm whether auto-announce is enabled on the server where this happens? The separate case where all users leave the voice channel does not appear to be the same issue from the code path I checked. That path should just disconnect the bot. If you are still seeing an actual process crash when users leave, please include the logs/stack trace for that specific case so we can investigate it separately. — Reply to this email directly, view it on GitHub <#1314 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A45UXR4DIRGTWXUOVA7CZPL4ZAK4VAVCNFSM6AAAAACYIQ3FJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DGNRYGIYDQOBYHE> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[shiftybitshiftr]

Thanks, these logs confirm the queue-empty auto-announce crash that #1316 is intended to fix.

The key parts are:

• the container is running 2.11.4 / commit 7837f4fa0611afbc3834dd52fc981b047b02c1d3
• the stack points at src/services/player.ts:670
• Discord rejected a send with embeds: [] as DiscordAPIError[50006]: Cannot send an empty message

That matches the bug where Muse advances past the final track and then tries to auto-announce a next song that does not exist. The PR image has the fix, so please test with this image instead of 2.11.4:

ghcr.io/museofficial/muse:pr-1316

For Docker Compose, temporarily set Muse's image to that tag, then run:

docker compose pull
docker compose up -d

If it still crashes on the PR image, please paste only the startup version/commit lines and the stack trace around the next crash. Those two pieces will tell us whether the PR image was actually running and whether there is a second crash path to fix.

[tinongskie]

I'm at the PR-1316 image now, I set the config-set-leave-if-no-listeners to false and the bot crashes. Here is the log 2026-05-20 11:55:20.727170+08:00 ======================================== 2026-05-20 11:55:20.727246+08:00======================================== 2026-05-20 11:55:20.727256+08:00================= muse ================= 2026-05-20 11:55:20.727264+08:00======================================== 2026-05-20 11:55:20.727271+08:00=========== Made with 🎶 by ============ 2026-05-20 11:55:20.727286+08:00==== https://github.com/codetheweb ===== 2026-05-20 11:55:20.727294+08:00======================================== 2026-05-20 11:55:20.727302+08:00======================================== 2026-05-20 11:55:20.727310+08:002026-05-20T03:55:20.727310073Z 2026-05-20 11:55:20.727317+08:00Running version 2.11.4 built on 5/4/2026 (commit 4944ba7) 2026-05-20 11:55:20.727329+08:002026-05-20T03:55:20.727329360Z 2026-05-20 11:55:20.727337+08:00🔧 Need help? https://github.com/codetheweb/muse/discussions/new 2026-05-20 11:55:20.727344+08:00🐛 Bug? https://github.com/codetheweb/muse/issues/new 2026-05-20 11:55:20.727352+08:00✨ New feature? https://github.com/codetheweb/muse/issues/new 2026-05-20 11:55:20.727364+08:00☕ Discussion? https://github.com/codetheweb/muse/discussions/new 2026-05-20 11:55:20.727372+08:00💰 Help me? https://www.paypal.me/codetheweb https://github.com/sponsors/codetheweb 2026-05-20 11:55:20.727420+08:002026-05-20T03:55:20.727420859Z 2026-05-20 11:55:20.727445+08:002026-05-20T03:55:20.727445549Z 2026-05-20 11:55:20.731078+08:00- Applying database migrations... 2026-05-20 11:55:21.353661+08:00✔ Database migrations applied. 2026-05-20 11:55:21.602691+08:00YT_DLP_VERSION=2026.03.17 (/opt/yt-dlp/bin/yt-dlp) 2026-05-20 11:55:21.663460+08:00- 📡 connecting to Discord... 2026-05-20 11:55:24.071623+08:00✔ Ready! Invite the bot with https://discordapp.com/oauth2/authorize?client_id=1498264779293200394&scope=bot%20applications.commands&permissions=36700160 2026-05-20 12:04:03.622383+08:00/usr/app/src/services/player.ts:394 2026-05-20 12:04:03.622479+08:00throw new Error('No songs in queue to forward to.'); 2026-05-20 12:04:03.622500+08:00^ 2026-05-20 12:04:03.622515+08:002026-05-20T04:04:03.622515584Z 2026-05-20 12:04:03.622585+08:00Error: No songs in queue to forward to. 2026-05-20 12:04:03.622651+08:00at default.manualForward (/usr/app/src/services/player.ts:394:13) 2026-05-20 12:04:03.622671+08:00at default.forward (/usr/app/src/services/player.ts:299:10) 2026-05-20 12:04:03.622687+08:00at default.onAudioPlayerIdle (/usr/app/src/services/player.ts:665:18) 2026-05-20 12:04:03.622715+08:00at AudioPlayer.emit (node:events:519:28) 2026-05-20 12:04:03.622731+08:00at AudioPlayer.set state ***@***.***/voice/src/audio/AudioPlayer.ts:362:8) 2026-05-20 12:04:03.622747+08:00at AudioPlayer.checkPlayable ***@***.***/voice/src/audio/AudioPlayer.ts:518:4) 2026-05-20 12:04:03.622762+08:00at <anonymous> ***@***.***/voice/src/DataStore.ts:124:27) 2026-05-20 12:04:03.622786+08:00at Array.filter (<anonymous>) 2026-05-20 12:04:03.622804+08:00at audioCycleStep ***@***.***/voice/src/DataStore.ts:124:27) 2026-05-20 12:04:03.622820+08:00at Timeout.<anonymous> ***@***.***/voice/src/DataStore.ts:142:3) 2026-05-20 12:04:03.622844+08:002026-05-20T04:04:03.622844191Z 2026-05-20 12:04:03.622860+08:00Node.js v22.22.2

…

On Fri, May 15, 2026 at 3:16 PM Michael ***@***.***> wrote: *shiftybitshiftr* left a comment (museofficial/muse#1314) <#1314 (comment)> Thanks, these logs confirm the queue-empty auto-announce crash that #1316 <#1316> is intended to fix. The key parts are: - the container is running / commit - the stack points at - Discord rejected a send with as That matches the bug where Muse advances past the final track and then tries to auto-announce a next song that does not exist. The PR image has the fix, so please test with this image instead of : For Docker Compose, temporarily set Muse's image to that tag, then run: If it still crashes on the PR image, please paste only the startup version/commit lines and the stack trace around the next crash. Those two pieces will tell us whether the PR image was actually running and whether there is a second crash path to fix. — Reply to this email directly, view it on GitHub <#1314 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A45UXR4EFW3A3WDFUPFBOID42274BAVCNFSM6AAAAACYIQ3FJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DINJXG44DSNBVGE> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[shiftybitshiftr]

Thanks, this log shows a different crash than the first one.

The PR image fixed the Cannot send an empty message crash, but Muse was still crashing when playback ended and there was no next song:

Error: No songs in queue to forward to.
at default.manualForward (/usr/app/src/services/player.ts:394:13)
at default.onAudioPlayerIdle (/usr/app/src/services/player.ts:665:18)

I pushed another update to #1316, and the PR image has rebuilt successfully.

Please pull the same image again:

ghcr.io/museofficial/muse:pr-1316

Then restart:

docker compose pull
docker compose up -d

After restart, the startup log should not show commit 4944ba759c343a09742c5f3840ffb2001009f529 anymore.

If it still crashes, please paste the new startup version/commit line and the new stack trace.

[tinongskie]

2026-06-05 12:22:18.292524+08:00======================================== 2026-06-05 12:22:18.292602+08:00======================================== 2026-06-05 12:22:18.292614+08:00================= muse ================= 2026-06-05 12:22:18.292623+08:00======================================== 2026-06-05 12:22:18.292633+08:00=========== Made with 🎶 by ============ 2026-06-05 12:22:18.292642+08:00==== https://github.com/codetheweb ===== 2026-06-05 12:22:18.292651+08:00======================================== 2026-06-05 12:22:18.292660+08:00======================================== 2026-06-05 12:22:18.292669+08:002026-06-05T04:22:18.292669844Z 2026-06-05 12:22:18.292678+08:00Running version 2.11.4 built on 5/20/2026 (commit 64b9ca7) 2026-06-05 12:22:18.292688+08:002026-06-05T04:22:18.292688116Z 2026-06-05 12:22:18.292696+08:00🔧 Need help? https://github.com/codetheweb/muse/discussions/new 2026-06-05 12:22:18.292705+08:00🐛 Bug? https://github.com/codetheweb/muse/issues/new 2026-06-05 12:22:18.292714+08:00✨ New feature? https://github.com/codetheweb/muse/issues/new 2026-06-05 12:22:18.292723+08:00☕ Discussion? https://github.com/codetheweb/muse/discussions/new 2026-06-05 12:22:18.292740+08:00💰 Help me? https://www.paypal.me/codetheweb https://github.com/sponsors/codetheweb 2026-06-05 12:22:18.292770+08:002026-06-05T04:22:18.292770868Z 2026-06-05 12:22:18.292797+08:002026-06-05T04:22:18.292797119Z 2026-06-05 12:22:18.296542+08:00- Applying database migrations... 2026-06-05 12:22:18.949042+08:00✔ Database migrations applied. 2026-06-05 12:22:19.199888+08:00YT_DLP_VERSION=2026.03.17 (/opt/yt-dlp/bin/yt-dlp) 2026-06-05 12:22:19.257015+08:00- 📡 connecting to Discord... 2026-06-05 12:22:58.678666+08:00✔ Ready! Invite the bot with https://discordapp.com/oauth2/authorize?client_id=1498264779293200394&scope=bot%20applications.commands&permissions=36700160 2026-06-05 12:28:04.570372+08:00/usr/app/node_modules/spotify-web-api-node/src/http-manager.js:47 2026-06-05 12:28:04.570465+08:00return new WebapiError(response.body, response.headers, response.statusCode, response.body); 2026-06-05 12:28:04.570486+08:00^ 2026-06-05 12:28:04.570497+08:002026-06-05T04:28:04.570497697Z 2026-06-05 12:28:04.570507+08:00WebapiError: [object Object] 2026-06-05 12:28:04.570518+08:00at _toError (/usr/app/node_modules/spotify-web-api-node/src/http-manager.js:47:10) 2026-06-05 12:28:04.570541+08:00at /usr/app/node_modules/spotify-web-api-node/src/http-manager.js:71:25 2026-06-05 12:28:04.570560+08:00at Request.callback (/usr/app/node_modules/superagent/src/node/index.js:902:3) 2026-06-05 12:28:04.570578+08:00at IncomingMessage.<anonymous> (/usr/app/node_modules/superagent/src/node/index.js:1130:18) 2026-06-05 12:28:04.570599+08:00at Stream.emit (node:events:519:28) 2026-06-05 12:28:04.570618+08:00at Unzip.<anonymous> (/usr/app/node_modules/superagent/src/node/unzip.js:54:12) 2026-06-05 12:28:04.570637+08:00at Unzip.emit (node:events:519:28) 2026-06-05 12:28:04.570656+08:00at endReadableNT (node:internal/streams/readable:1698:12) 2026-06-05 12:28:04.570675+08:00at process.processTicksAndRejections (node:internal/process/task_queues:89:21) { 2026-06-05 12:28:04.570719+08:00body: {}, 2026-06-05 12:28:04.570741+08:00headers: { 2026-06-05 12:28:04.570768+08:00'cache-control': 'private, max-age=0', 2026-06-05 12:28:04.570778+08:00'access-control-allow-origin': '*', 2026-06-05 12:28:04.570787+08:00'access-control-allow-headers': 'Accept, App-Platform, Authorization, Content-Type, Origin, Retry-After, Spotify-App-Version, X-Cloud-Trace-Context, client-token, content-access-token', 2026-06-05 12:28:04.570797+08:00'access-control-allow-methods': 'GET, POST, OPTIONS, PUT, DELETE, PATCH', 2026-06-05 12:28:04.570807+08:00'access-control-allow-credentials': 'true', 2026-06-05 12:28:04.570816+08:00'access-control-max-age': '604800', 2026-06-05 12:28:04.570825+08:00'content-encoding': 'gzip', 2026-06-05 12:28:04.570836+08:00'strict-transport-security': 'max-age=31536000', 2026-06-05 12:28:04.570845+08:00'x-content-type-options': 'nosniff', 2026-06-05 12:28:04.570854+08:00'alt-svc': 'h3=":443"; ma=2592000,h3-29=":443"; ma=2592000, h3=":443"; ma=2592000', 2026-06-05 12:28:04.570864+08:00date: 'Fri, 05 Jun 2026 04:28:04 GMT', 2026-06-05 12:28:04.570873+08:00server: 'envoy', 2026-06-05 12:28:04.570883+08:00via: 'HTTP/2 edgeproxy, 1.1 google', 2026-06-05 12:28:04.570892+08:00connection: 'close', 2026-06-05 12:28:04.570901+08:00'transfer-encoding': 'chunked' 2026-06-05 12:28:04.570910+08:00}, 2026-06-05 12:28:04.570919+08:00statusCode: 403 2026-06-05 12:28:04.570928+08:00} 2026-06-05 12:28:04.570937+08:002026-06-05T04:28:04.570937967Z 2026-06-05 12:28:04.570947+08:00Node.js v22.22.3

…

On Wed, May 20, 2026 at 12:53 PM Michael ***@***.***> wrote: *shiftybitshiftr* left a comment (museofficial/muse#1314) <#1314 (comment)> Thanks, this latest log confirms a second queue-empty crash path, and it is different from the earlier Discord 50006 empty-message crash. The key lines are: Running version 2.11.4 built on 5/4/2026 (commit 4944ba7) Error: No songs in queue to forward to. at default.manualForward (/usr/app/src/services/player.ts:394:13) at default.forward (/usr/app/src/services/player.ts:299:10) at default.onAudioPlayerIdle (/usr/app/src/services/player.ts:665:18) That means the PR image did get past the previous empty auto-announce send, but the idle handler could still call forward(1) when there was no queue entry left to advance to. In that case Muse should finish the queue and go idle, not throw. I pushed another update to #1316 <#1316> for this path. The refreshed PR image checks are green, so please pull the same PR image again: ghcr.io/museofficial/muse:pr-1316 For Docker Compose: docker compose pull docker compose up -d After restarting, the startup line should no longer show commit 4944ba7; the refreshed PR image was built from merge commit 64b9ca7. If it still crashes, please paste the startup version/commit lines and the new stack trace again. Those two pieces are enough to confirm whether the refreshed image is running and whether there is another remaining crash path. — Reply to this email directly, view it on GitHub <#1314 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A45UXR3NCPY3CM5GZVFPC5343U23BAVCNFSM6AAAAACYIQ3FJWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DIOJUGYZTCNBWG4> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[shiftybitshiftr]

Thanks, this confirms the refreshed PR image is running. This latest stack is a new issue: the queue-empty crash paths fixed in #1316 are no longer showing up, and the current crash is a Spotify API 403 from spotify-web-api-node. I’m going to land #1316 for the confirmed queue-empty fixes, then handle this Spotify crash separately.

[shiftybitshiftr]

Released in v2.11.5: the confirmed queue-empty crash fixes from #1316 and the Spotify 403 crash hardening from #1321 are now available.

Please update to ghcr.io/museofficial/muse:2.11.5 or pull :latest, then let us know if any crash remains. If it still happens, please include the startup version/commit line and the new stack trace.