Summary
ERROR TO LAUNCH FLOW, LAUNCH FLOW DIFFERENT TO THE SELECTED
Question
We have two flows, and when I launched the flow “INTEGRACION Restart PROTEOCANAL Each CPD Init”, the HPOO launches the flow of “INTEGRACION Restart Neti Jboss Init”, this error not is always, but this is a critical error, because we can’t control what flow is launch.
Answer
Behavior for displayed Run Name in the Flow Launcher page is like this:
- The Run Name is cached as the last value setup in the field that was ran with. (last run name of this flow)
- It is stored in the local cache of the machine , so it is available cross-session (even if session ends) and is available also to any user that logs in to that specific machine
- But it is not stored on the server side , that’s why when you press CTRL+F5, it will force fetching the default value from Server (not from machine’s cache)
- You can always Reset this value to the default – “Flow name”
- Most probably , due to pages loading delayed at some point ( CPU or disk usage high) , and switching fast from one flow to the other in the Library tree, the value of some of the flow’s Run Names were not updated correctly. This wrong value was the one used to run the flow once, so being cached, it showed it wrong until pressing Reset button.
- The Run Name is cached as the last value setup in the field that was ran with. (last run name of this flow)
- It is stored in the local cache of the machine , so it is available cross-session (even if session ends) and is available also to any user that logs in to that specific machine
- But it is not stored on the server side , that’s why when you press CTRL+F5, it will force fetching the default value from Server (not from machine’s cache)
- You can always Reset this value to the default – “Flow name”
- Most probably , due to pages loading delayed at some point ( CPU or disk usage high) , and switching fast from one flow to the other in the Library tree, the value of some of the flow’s Run Names were not updated correctly. This wrong value was the one used to run the flow once, so being cached, it showed it wrong until pressing Reset button.