Skip to content

Troubleshooting

Jump to bottom
alienfactor edited this page Aug 8, 2026 · 1 revision

This page covers common problems with Queue Pop Notifier and the most useful checks to perform before opening an issue.

No notification arrives

First determine where the notification chain stops.

World of Warcraft
       ↓
Queue Pop Notifier add-on
       ↓
Windows companion client
       ↓
Notification service
       ↓
Smartphone

1. Test the notification service

Open the Windows companion client settings and use Test service for the active provider.

If the test notification does not arrive, the problem is with the notification service configuration rather than WoW queue detection.

See Notification Services.

2. Test the complete notification chain

Inside World of Warcraft, enter:

/qpn test

If the service test works but /qpn test does not, continue with the game detection checks below.

World of Warcraft is not detected

Check that:

  • World of Warcraft is running
  • the game is not minimized
  • the game window is visible on screen
  • the relevant part of the game window is not fully covered by another application
  • the Queue Pop Notifier add-on is enabled

If the game is already running but is still not detected, restart the Windows companion client.

Detection is interrupted or unreliable

Queue Pop Notifier detects a small visual signal generated by the WoW add-on.

Detection can be interrupted if Windows cannot capture the required area of the game window.

Typical causes include:

  • World of Warcraft is minimized
  • another window completely covers the relevant area
  • a Windows security or UAC screen is active
  • the game window temporarily cannot be captured

Return to the game, make sure it is visible, and check the client status again.

/qpn test does not work

Inside World of Warcraft, first enter:

/qpn

Confirm that Queue Pop Notifier is enabled.

If it is disabled, enter:

/qpn on

Then try again:

/qpn test

If the add-on does not respond to /qpn, verify that it is enabled in the World of Warcraft AddOns list.

Pushover test fails

Check:

  • User Key
  • API Token
  • internet connection
  • that Pushover is selected as the active notification service

Then use Test service again.

See Notification Services.

ntfy test fails

Check:

  • Topic
  • Server address
  • internet connection
  • that ntfy is selected as the active notification service

For the public ntfy service, the server is normally:

https://ntfy.sh

Make sure the same topic is configured in your ntfy smartphone app.

See Notification Services.

Telegram test fails

Check:

  • Bot Token
  • Chat ID
  • internet connection
  • that Telegram is selected as the active notification service

Make sure you have opened the bot in Telegram and sent it at least one message.

Then use Test service again.

See Notification Services.

The wrong notification service is used

Queue Pop Notifier can store configuration for multiple services, but only one service is active at a time.

Open the settings and verify that the intended provider is selected as the active/default notification service.

Save the settings and run Test service.

Settings are lost or incorrect

Queue Pop Notifier stores its settings locally under:

%APPDATA%\QueuePopNotifier

Do not share configuration files publicly if they contain notification-service credentials.

Windows SmartScreen blocks the application

The Windows companion client is currently not digitally signed, so Microsoft Defender SmartScreen may display an Unknown publisher warning.

See Windows SmartScreen.

Only download QueuePopNotifier.exe from the official GitHub Releases page.

The client does not start

Try the following:

  1. Close any existing Queue Pop Notifier instance.
  2. Start QueuePopNotifier.exe again.
  3. Check the Windows system tray.
  4. If Windows SmartScreen appears, see Windows SmartScreen.
  5. Download the latest release again if the executable may be incomplete or damaged.

Latest Queue Pop Notifier Release

Auto-start with Windows does not work

Open Queue Pop Notifier settings and disable Start with Windows.

Save the settings, enable the option again, and save once more.

Then restart Windows and check whether Queue Pop Notifier appears in the system tray.

Notifications worked before but suddenly stopped

Check the notification chain in this order:

  1. Use Test service in the Windows client.
  2. Run /qpn test inside World of Warcraft.
  3. Make sure World of Warcraft is visible and not minimized.
  4. Check that the intended notification service is active.
  5. Restart the Windows companion client.
  6. Check whether a newer Queue Pop Notifier version is available.

Still not working?

Open an issue in the GitHub repository:

Report an issue

Please include:

  • Queue Pop Notifier client version
  • World of Warcraft version
  • notification service used
  • current client status
  • whether Test service works
  • whether /qpn test works
  • a short description of what happens

Do not include passwords, API tokens, User Keys, Bot Tokens, Chat IDs, or other private credentials.

Clone this wiki locally