To add to @alinder’s very useful info…
Fixlets the client has already evaluated are “old content” and are re-evaluated as part of the normal client loop.
New fixlets (including new actions) are “new content” and get moved to the front of the client’s evaluation loop. So the client will report action status with a higher priority, but doesn’t go back to evaluate the original source fixlet until that fixlet’s turn comes back through the loop.
One way to make the client move through its evaluation loop more quickly is to increase the cpu utilization on the client. By default the client is throttled to only use 2% of one processor core, so it runs in the background without interfering with anything else running on the computer. You could increase that throttle to let the client evaluate content faster, at the cost of using more CPU on the client.
Another thing you could do is to force the client to refresh. This checks that the client has the latest version of every site, re-evaluates every fixlet and analysis property, and sends up a full report. You shouldn’t do this frequently as it puts more workload on the relay and root server, but if (for example) you need a full re-evaluation after a monthly patch baseline, you could include a task at the end to force a full evaluation. You can do that with the actionscript command
notify client forcerefresh