KB13059: History list messages appear with a status ‘Processing on another node’ in a clustered MicroStrategy Intelligence Server environment

SYMPTOM:
Users in a clustered Strategy Intelligence Server environment may notice that history list messages appear with the status 'Processing on another node', as shown below:
 

 
On attempting to view the history list message, the user is presented with the prompt screen for the report with none of the original prompt selections shown.
 
STEPS TO REPRODUCE:
Follow the steps below to reproduce this issue:
 

1. Turn on the option to send reports automatically to history list on execution
2. Log in using Strategy Web or Desktop and log into different servers in the cluster simultaneously
3. Execute a report on one of the servers. Now it will appear in the history list.
4. Open the session connected to the clustered Strategy Intelligence Server that is not running the report, and the report appears with a status 'Processing on another node'. Attempt to execute the report. The user is re prompted for the report (if there are any prompts for the same.)

CAUSE:
Due to history list synchronization, the status of the history list is synchronized on both the clustered Strategy Intelligence Servers. One should show the report as executing, and the other would show the report as processing on the first node.
 
If the user tried to execute the history list report from the second node, the report will be executed again, as the results from the first execution are not returned yet, and will be re-prompted for the report prompt answers.
 
ACTION:
If possible, ensure that users do not open multiple sessions - i.e. that they are connected to only one Strategy Intelligence Server at a time. If the users do open multiple sessions and see this behavior, advise the users to wait for the report to complete execution before attempting to view the results.