I think we’re are mixing terms. Usually we still about a Fixlet/Task being Relevant, which is just based on the relevance statements of the task/Fixlet.
I think you’re mostly describing the Action applicability though - which is based on both the original Fixlet/task applicability, as well as whether the action was targeted against the machine, whether the action has already executed, etc.
If sending a new action from the same source Fixlet is working, then what you likely need to set are the Retry or Reapply options in the ‘Take Action’ dialog.
You probably need either “Reapply whenever it becomes relevant again”, or “Reapply while relevant, waiting X minutes between reapplications”.
You can use the first case of the original Fixlet toggles to Not Relevant when you run the action, and then switches back to Relevant later. Like, if you wanted to repeatedly remove Chrome every time the user reinstalls it. This task is Relevant when Chrome is installed, executing the action removes Chrome and toggles the Fixlet to Not Relevant, and if the user reinstalls Chrome it becomes Relevant again and the action re-executes.
You’d use the second option if the original Fixlet does not switch to Not Relevant when you run the action. Like if you wanted to execute an Inventory scan once a day. The Relevance for the task is just “I have Inventory Scanner installed”, and that does not change to ‘Not Relevant’ after executing a scan…you need this task to "Reapply while relevant, waiting 1 day between reapplications’
If you don’t specify any reapply at all, the action runs exactly one time and never tries again.