I experienced a behaviour with Multicorder which may be unavoidable, but thought I should report it in case there is a workaround.

Was using the Multicorder to save isos of various inputs:

4 x HDSDI through a Blackmagic Decklink
1 x NDI, vmix desktop capture from another machine.

All SDIs at 50mbit H264 (CPU, not Hardware encode), NDI just saving it's MOV.

One of the cameras on HDSDI was coming in via a Teradek Bolt. The camera op needed to switch out Vlock batteries, so the power to the Teradek dropped.
The bolt receiver does some kind of refresh, I think maybe it defaults to a different resolution / frame rate or something.
The input in vMix reacts to this, flickers, not sure exactly what it's doing.

The Multicorder stopped, threw up an error. I can't remember exactly what, we were live and everything else was working fine so I just had to get on with it.

I can't recreate this to further test and isolate exact conditions as the Teradek Bolt was rented and went back immediately after the gig.

It's understandable that a recording would fail if a HDSDI source did suddenly change it's resolution or something. However it's a shame that it causes all the records to stop, or that it doesn't just self restart when a source returns.

Worth noting that the computer was well within it's capabilities, CPU barely above 15%, GPU memory 50%ish, recording to nvme SSD.
The 2 main recordings, live stream, external output (Blackmagic Decklink), both independant Full screens, all continued completely unaffected as far as I'm aware.
I was sending output 1 as a SRT feed to one of the camera ops, he did report that it dropped out for him but recovered quickly.

Is this expected behaviour, and is there a workaround? Let me know if I can provide any more info.

Cheers
Andrew