I posted my current approach at a workaround on this issue here…
It basically tests the current config settings against the prior settings, and then only proceeds when a change has been made. This isolates the component from successive executions unless it is triggered by a change to the configuration setting. At that point it only functions 1 time, and then returns to bypass.