Recorder capture Not working in production

​@Ajith 9655 Your mission, should you choose to accept it, is to determine what is different between the systems. It could be as small as a revision in the browser, operating system, or application; color depth, zoom scale, account permissions…

You get the idea. This is why many companies use identical VMs for development and production -- so there are zero differences. 

I'm experiencing the same issue. It works correctly in the development environment, but not in production. I've reviewed everything and couldn't identify any differences.

​@jahdai.justin If there are no differences, the bot will run. Identifying those differences is the hard part -- and why companies use VMs for dev and prod. 

You can start by identifying WHY the bots are failing. Is it unable to find a control on a web page? If so, compare the DOMXPaths from the dev workstation to the prod bot runner. 

There is a difference, but finding it isn't always easy. 

Hi ​@Ajith 9655,

What is your bot runner screen resolution? 

What did you mean by not working? Are you getting any errors for recorder actions? If so, please share for a better understanding.

​@Ajith 9655 , generally I have witnessed it, the Dev instance of a particular application is different than a production instance, even if it looks exact the backend is a but different, can you please compare if the end application is same for both dev or production is same or different

Hi ​@Ajith 9655 ,

Do you have more details about the error?

What do you mean with “not working”?

I experienced a new error this week, related to the recorder package as well, after (what I guess it was) a Windows update. I found the solution using this community, searching by the error message:

“Object condition command has experienced an internal error.”

If you have any information that you can share, more than happy to help you!

Thanks,
Daiana