Queued messages can get stuck while an inactive session remains in Running state after completion

Short summary

No response

Affected version or release

v1.1.15

Installation context

GitHub Copilot desktop app for Windows

What happened?

Queued messages intermittently get stuck because the active session continues to show Running even though no work appears to be happening.

The queued message remains visible in the queue and is not sent automatically. Clicking Send now fails with this error:

Queued message was not sent. Check the updated queue and try again.

The session remains in the running state, leaving no working way to dispatch the queued message.

Steps to reproduce

1. Open a session in the GitHub Copilot desktop app.
2. While the session is running, queue another message.
3. Wait until the active session appears to have finished all work.
4. Observe that the session still shows Running even though nothing is happening, and the queued message is not sent.
5. Open the queue and click Send now.
6. Observe the error: Queued message was not sent. Check the updated queue and try again.

The issue occurs intermittently.

Expected behavior

When the active session finishes, its status should change from Running and the next queued message should be sent automatically. If a message remains queued, clicking Send now should dispatch it successfully.

Additional context

• Platform: Windows
• Frequency: Intermittent
• A screenshot of the Send now error is available and will be attached to this issue.