Hello Sam,
In general, a similar recorder behavior can be seen when FMSTR_Recorder() is not called periodically by the MCU application - so its state machine is not running.
I see that you use the Matlab Model-based design toolbox. I'm not an expert here, but I think the "Recorder Call" should be put in a block which is triggered periodically, e.g. by an interrupt. You can check the generated C code to see how is the FMSTR_Recorder() called.
I also recommend to refer to a MBDT Motor Control demo which makes use of an interrupt-driven recorder. If you need a further help, I will ask someone from MBDT team to step in.
Regards,
Michal