Taskbar doesn't flash / show badge when window is closed (works fine when minimized) - Desktop 6.2.2

Troubleshooting
1

Summary
When I close the app window using the X button, the app keeps running in the system tray, but the taskbar icon does not flash and no red unread badge appears when a new message arrives. Windows toast notifications (pop-ups) still work correctly. When I minimize the window instead of closing it, taskbar flashing and the red badge work exactly as expected.

Environment

  • Mattermost Desktop version: 6.2.2
  • Mattermost Server version: 11.7.7
  • OS: Windows 11 (Korean locale)

Steps to reproduce

  1. Open the Mattermost desktop app and log in
  2. Close the window using the X button (app remains in the system tray)
  3. Have another user send a direct message or mention
  4. A native Windows toast notification appears correctly
  5. Taskbar icon does not flash and no red badge/count appears

Expected behavior
Taskbar icon should flash and/or display a red badge with the unread count, the same way it does when the window is minimized instead of closed.

Observed behavior
No taskbar indication at all after closing the window via X — only works correctly when minimized.

What I’ve already checked/tried (no change in behavior)

  • Notifications settings: “Show red badge on taskbar icon to indicate unread messages” — ON
  • Notifications settings: “Flash taskbar icon when a new message is received” — ON
  • General settings: “Leave app running in notification area when application window is closed” — ON (restarted the app after enabling)
  • Windows Notifications settings: Mattermost is allowed to send notifications (toggled off and back on to reset)
  • Task Manager: disabled “Efficiency Mode” for the Mattermost process — no change
  • Windows Accessibility > Audio > “Flash the screen during audio notifications” — checked, no change
  • Confirmed via Task Manager that the Mattermost process remains running after closing the window (not killed)
  • Checked for Group Policy restrictions on notification settings — none found
  • Full clean reinstall: uninstalled the app, deleted the entire %appdata%\Mattermost folder (config, cache, local storage), reinstalled the latest 6.2.2 MSI from scratch. Issue persists exactly the same, ruling out a corrupted local config/cache.

I’ve gone through all the standard troubleshooting steps I could find, including a similar case reported here previously ([Solved] Desktop client does not notify when new messages arrive), but none of the suggested fixes resolved the issue. Wondering if anyone else on 6.2.2 has run into this, or if there’s a known workaround.

Thanks in advance!

2

Welcome to the community, NEXCODE, and thanks for the exceptionally thorough troubleshooting! This to me looks like a possible Desktop App issue, so please share your Windows 11 build and sanitized logs using our Desktop App troubleshooting guide, with minimizing the window as the best workaround for now.

3

Hi John, thank you for your response.

Windows 11 Build: 26200.9168

I reproduced the issue with the console open. Here’s the log output during the notification test:

index.ts:175 Loading plugin github, version 2.7.1
index.ts:159 Loaded plugin github, version 2.7.1
websocket_actions.ts:185 Initializing or re-initializing WebSocket
websocket.js:105 websocket connecting to wss://chat.nex-code.co.kr/api/v4/websocket
/api/v4/trial-license/prev:1  Failed to load resource: the server responded with a status of 403 (Forbidden)
/api/v4/trial-license/prev:1  Failed to load resource: the server responded with a status of 403 (Forbidden)
websocket.js:284 got connection id  qfixhsnzx3fhimr93m6hqxx1pe
client4.js:2211  GET https://chat.nex-code.co.kr/api/v4/trial-license/prev 403 (Forbidden)
(anonymous) @ client4.js:2211
(anonymous) @ client4.js:2207
getPrevTrialLicense @ client4.js:1876
(anonymous) @ admin.ts:450
(anonymous) @ redux-thunk.mjs:5
(anonymous) @ redux.mjs:331
(anonymous) @ product_menu_list.tsx:93
Rj @ react-dom.production.min.js:244
Ik @ react-dom.production.min.js:286
Fk @ react-dom.production.min.js:273
jg @ react-dom.production.min.js:127
Rk @ react-dom.production.min.js:274
Jb @ react-dom.production.min.js:52
hd @ react-dom.production.min.js:109
fd @ react-dom.production.min.js:74
ed @ react-dom.production.min.js:73
client4.js:2211  GET https://chat.nex-code.co.kr/api/v4/trial-license/prev 403 (Forbidden)
(anonymous) @ client4.js:2211
(anonymous) @ client4.js:2207
getPrevTrialLicense @ client4.js:1876
(anonymous) @ admin.ts:450
(anonymous) @ redux-thunk.mjs:5
(anonymous) @ redux.mjs:331
(anonymous) @ product_menu_list.tsx:93
Rj @ react-dom.production.min.js:244
Ik @ react-dom.production.min.js:286
Fk @ react-dom.production.min.js:273
jg @ react-dom.production.min.js:127
Rk @ react-dom.production.min.js:274
Jb @ react-dom.production.min.js:52
hd @ react-dom.production.min.js:109
fd @ react-dom.production.min.js:74
ed @ react-dom.production.min.js:73
client4.js:2211  GET https://chat.nex-code.co.kr/api/v4/trial-license/prev 403 (Forbidden)
(anonymous) @ client4.js:2211
(anonymous) @ client4.js:2207
getPrevTrialLicense @ client4.js:1876
(anonymous) @ admin.ts:450
(anonymous) @ redux-thunk.mjs:5
(anonymous) @ redux.mjs:331
(anonymous) @ product_menu_list.tsx:93
Rj @ react-dom.production.min.js:244
Ik @ react-dom.production.min.js:286
Fk @ react-dom.production.min.js:273
jg @ react-dom.production.min.js:127
Rk @ react-dom.production.min.js:274
Jb @ react-dom.production.min.js:52
hd @ react-dom.production.min.js:109
fd @ react-dom.production.min.js:74
ed @ react-dom.production.min.js:73
team_controller.tsx:85 computer woke up - reconnecting
websocket_actions.ts:258 Reconnecting WebSocket

Is this the kind of log output you’re looking for?