Strange Stream deck 'Start a cue' behaviour

[sounds...@gmail.com]

Getting some strange behaviour when trying to use the 'Start a Cue' item using the QLAB stream deck plugin and I'm hoping by opening it up to a wider audience I might find a solution (or  at least a why). Worked on this with the lovely QLAB support guys, but even with me providing my stream deck profile files they weren't able to recreate the error their end. I've also spoken with the folks at corsair and they have 'forwarded it on to their senior dev team'.

Although I'm demonstrating using the virtual stream deck this is purely in order to do an easy recording, the behaviour is the same using the physical stream deck. In fact, most of the time I am able to get one 'Start a Cue' trigger to work and then I get the hazard symbol on any button press once I've added a second instance. As you'll see, the OSC cues are working fine (which somewhat negates my need for the 'Start a Cue' trigger, but it's frustrating and I'd love to get to the bottom of it.

Let me know if there are any details that I can add

Will attach a screen recording once message has posted, running up against a 'message too long' error.

I'm running:

QLAB 5.5.6

Stream Deck 7.0.3

MacBook Air M4

Seqouia 15.7.2

[sounds...@gmail.com]

https://www.icloud.com/iclouddrive/0f3xWFpGBaqzwJBN0rOzi5n9g#Screen_Recording_2025-11-11_at_14.21