Click Properties

I recently encountered an issue where the SimulateClick properties in my click activities were no longer working as of yesterday, so I switched to using SendWindowMessages, which resolved the problem. I typically use the Edge browser for my tasks. Does anyone know why this change occurred? Could it possibly be due to an Orchestrator upgrade, and if so, how would that have affected it?

Hi @manipreethi410

It may be because the element you were obtaining has changed in some of its characteristics, or also the page/application you were using, and the SimulateClick was not accepted by this element, either of the two properties is fine and they work in the background

Regards!

@manipreethi410

Two possible reasons

  1. Did you use wait for load complete? If not sometimes there might be latency and even if click is passed to website it would not have taken it because it is still loading
  2. As mentioned by @fernando_zuluaga there might be some changes to the web app which caused it to not accept simulate

Cheers

Thank you, Its not because of orchestator Upgrade right?

1 Like

Exactly, probably the updates have nothing to do with it

Regards

Thank you for the confirmation