KB37848: When placing a project into Idle mode from the Project Monitor, the project remains unloaded and does not become Idle on nodes where it is not loaded in MicroStrategy 9.x and higher.

SYMPTOM:
In Strategy 9.x and higher, users notice that when placing a project into Request Idle or Full Idle mode from the Project Monitor, changes are not propagated correctly across all nodes in an asymetrical cluster.     
 
For example, a user may place a project into Request Idle mode from the Project Monitor:
 

 
After doing this, the project becomes Idle on the node where the action was performed, but remains Unloaded on the second cluster node.
 
CAUSE:
This is a known issue in Strategy 9.x and higher.
 
ACTION:
Currently this issue is being reviewed by Strategy for a potential code fix on an upcoming Strategy release.
 
WORKAROUND:
Users can first load the project on the node where the project you wish to Idle is unloaded before placing it into Request Idle.