CC1352P: multple CMD_TRIGGERS, odd behavior

Hi! trying to use a few RX TRIG_NEVERs with CMD_TRIGGER in a short chain
I shared the code below

I've set up a scope with a gpio toggle, and I can see only one of my 2 RXs responds to CMD_TRIGGER. 
When I use distinct triggerNo's, only my first RX responds. 
When I used the same triggerNo's (sanity check), they would alternate which responded. 

The point is, I'm only really able to use CMD_TRIGGER + TRIG_NEVER once at a time. 
I am sure I'm doing something wrong here. 
Has anybody used multiple CMD_TRIGGERS simultaneously or sequentially?

            cmdRx1->startTrigger.triggerType    = TRIG_NOW;
            cmdRx1->endTrigger.triggerType      = TRIG_NEVER;
            cmdRx1->endTrigger.bEnaCmd          = 1;
            cmdRx1->endTrigger.triggerNo        = 1;

//...

            cmdRx3->pNextOp                     = NULL;
            cmdRx3->startTrigger.triggerType    = TRIG_NOW;             
            cmdRx3->endTrigger.triggerType      = TRIG_NEVER;            
            cmdRx3->endTrigger.bEnaCmd          = 1;
            cmdRx3->endTrigger.triggerNo        = 0;
            
// ...

void killRx1(void) { 
    rfc_CMD_TRIGGER_t triggerCmd1 = {
        .commandNo = CMD_TRIGGER,
        .triggerNo = 1
    };
    RF_runImmediateCmd(rfHandle, (uint32_t*)&triggerCmd1);
}

void killRx3(void) { 
    rfc_CMD_TRIGGER_t triggerCmd2 = {
        .commandNo = CMD_TRIGGER,
        .triggerNo = 0
    };
    RF_runImmediateCmd(rfHandle, (uint32_t*)&triggerCmd2);
}