So, detailed in this article where I was attempting to get a simple Workflow triggered, I've done a clean install of v12 OpManager and am still getting similar results.

Basically we have a process that we wish to monitor.  A combination of code bug, yet to be determined, and when certain calls come in cause the process to start spawning out-of-control.  Rarely will we have more than 5-7 of these processes with an average of about 4-5.

So as per the article above, did the same and created a new Process monitor that checks for the process .exe, no path, no arg and set the Instance count threshold to be => 20 with a rearm hit of 10 and an recurrence count of 2 for the given windows system.

Next I create a Workflow that restarts a service, set the service and then send an Email with result.  Clicking on Trigger I can scroll and Process Monitors is checked, however, the specific process monitor I created is not.  If I check it, click Next and then save, if I go back in and edit again, that specific process monitor is NOT checked.

Since it is not binding to the Process monitor, it never gets triggered.

Verified that manually executing workflow functions (service is restarted and email sent).   If process count exceeds 20 for 2 pollings an alert is raised and we get a notification on it, however, the workflow never triggers.

I'm obviously missing something simple, but can't figure it out and it has spanned both v11 and now v12.