Alternative way of sending #ctrlclick

I have a test that works perfectly on my local (WIN 7) but fails on my test server (WIN server 2016). The step it fails at is ctrl+click-ing on an expand-entity in chrome. When I run this macro locally, everything works as expected. But the same macro fails to expand the entity on my test server. I get no errors… as Kantu thinks that it successfully executed the step… but the browser does not display what kantu is expecting next and hence it times out.

Here is the step in question:

{
  "Command": "XClick",
  "Target": "id=appstreaming_testExpandReportingEntity",
  "Value": "#ctrlclick"
},
{
  "Command": "pause",
  "Target": "1000",
  "Value": ""
},
{
  "Command": "XClick",
  "Target": "id=editv2018-appstreaming_test",
  "Value": "#ctrlclick"
}

Please note that I have 2 #ctrlclick steps in my macro - and ONLY THE FIRST ONE FAILS. If during execution, I manually crtrl+click to expand the entity, my macro continues on the execution without issues. Since this is neither my application’s issue nor Kantu’s issue… I’m here asking if there is another way of sending ctrl+click? May be simulate press_and_hold for ctrl key and then click?

Never mind this… I switched to firefox and this issue doesn’t occur anymore