RMS Patching Deployment Process Scheduling stops manually trigged runs?

Trying to figure out if this just a my environment issue and any ideas on how to resolve or work around it.
Currently, we have a few dozen apps that have deployment processes configured in RMS Patching. Most of these are configured to run on a schedule, after patch Tuesday to coincide with our Microsoft monthly patching maintenance windows. And this works great for us for monthly patching.

However, as we all know sometimes apps need to be patched out of cycle if a critical update is released.

So here is the issue, it seems that any of our deployment processes that have scheduling enabled, will not run correctly when the process is triggered to run outside of the scheduled run. We just see the “Successful” status, but nothing is imported into MCM.

Has anyone else experienced this? Have a work around, other than turning off the schedule and then turning it back on?

My understanding is that this is no longer an issue within the March release. Attached are the release notes. Recast Software v5.11 Releases