Is the Fixlet itself showing up as non-relevant (no applicable computers), or do the computers report Not Relevant when you push it as an Action?
I had a similar problem when i was trying to manage a fixlet relevance in this way, based on relevant baselines in a site. I think it has to do with the value of “site” or “action” losing context when the Action becomes active.
I’m doing something similar, but I’m basing the relevance on Pending Actions with a particular Constraint. I constrain my patching actions such that they only execute when a Client Setting “PatchWindowState” is not set to “closed”. I have the Action try three times before giving up, so now it’s no longer Pending. When there are no remaining Pending actions, I change the client’s PatchWindowState to Closed, which also unsubscribes from my catch-up site.
As for the number of open actions … I think that warning there has to do with responsiveness of the Console, which will try to retrieve status on all visible Actions when you open it. In a whitepaper IBM gave me on Patch Catch-Up, one of the recommendations was to use a dedicated Operator account to deploy catch-up patching. The CatchupOperator would have management rights assigned based on a Catch-Up Property on the client. When the client is caught-up, in addition to unsubscribing from the site containing the patch baselines, it would also unsubscribed from the catch-up operator account so it is no longer evaluating the Actions as well.