Actions not reaplying as expected

[fermt]

I have built a Fixlet that detects if a process is running on windows machines and if so it will issue a command to kill the process. I have deployed the Fixlet as a policy, with the settings

• Reapply this action

• While Relevant, wait 15 min

• Unlimited

I have tested on my machine and the policy works fine during the first and second execution.
When I execute the applications that creates the process, I receive the action and the process is terminated. I then re-open the application and the action is triggered once again. I then re-open the application and the action doesn’t become relevant until a few hours later. However, I can see that the Source Fixlet becomes relevant.

If I restart the agent, the action will become relevant right away. And it will run a couple of times right away but not more.

Am I correct expecting that the action becomes relevant every time the process is detected?

This is my relevance:

windows of operating system and (Exists processes Whose (name of it as string as lowercase = "processname.exe" as lowercase))

References:

Understanding "Reapply" behavior for Fixlets/Tasks that stay relevant

(imported topic written by BenKus) Sometimes you want certain Fixlets/Tasks actions to run periodically using the reapply and “Wait between” options in BigFix Take Action Dialog and you may notice that certain versions of BigFix behave differently. As an example, you might want to set a custom Task that writes out the command “netstat” to a file nightly so you can use relevance to examine the results. In general, the way to do this would be to make a Task with relevance of name of operating …

Solution for Actions not reapplying as expected

If you want an action to reapply, those that stay relevant won’t reapply unless a particular setting is used: [image] This seems to be where this behavior is first discussed: Understanding "Reapply" behavior for Fixlets/Tasks that stay relevant Using this setting basically forces the issue by making the action become non-relevant for a period of time after it is run. This would be a bad thing if it were an action that should only run once, but could be the desired case, like for some offers…

[orbiton]

I had something similar with another Client - I think you should Determine the Client Evaluation Cycle with Client Usage Profiler and Client Debug Logging - https://bigfix-wiki.hcltechsw.com/wikis/home?lang=en#!/wiki/BigFix%20Wiki/page/Slow%20and%20Unresponsive%20Clients%20-%20Troubleshooting

There is also another possibility - The Client CPU Utilization was tweaked and it could cause issues with the evaluation cycle - https://help.hcltechsw.com/bigfix/9.5/platform/Platform/Config/c_client_cpu.html

[fermt]

I am still not able to make this work as expected. I had done this in previous BigFix environments(with older versions) and the policies used to work just fine. I am just not able to make it work with the current environment running the latest V10. I have increased the CPU Utilization for testing and even with that the behavior is very random.

[orbiton]

What about I had something similar with another Client - I think you should Determine the Client Evaluation Cycle with Client Usage Profiler and Client Debug Logging - https://bigfix-wiki.hcltechsw.com/wikis/home?lang=en#!/wiki/BigFix%20Wiki/page/Slow%20and%20Unresponsive%20Clients%20-%20Troubleshooting1 ?