Skip to main content
Cadet | Tier 2
November 8, 2025
Solved

Recorder capture Not working in production

  • November 8, 2025
  • 8 replies
  • 211 views

Object capturing is not working in production, Where as in Dev environment it's working fine both the machine have same configuration 

    Best answer by Daiana Grimi

    Object capturing is not working in production, Where as in Dev environment it's working fine both the machine have same configuration 

    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

    8 replies

    Aaron.Gleason
    Automation Anywhere Team
    Automation Anywhere Team
    November 8, 2025

    @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. 

    jahdai.justin
    Cadet | Tier 2
    November 8, 2025

    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.

    Aaron.Gleason
    Automation Anywhere Team
    Automation Anywhere Team
    November 8, 2025

    @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. 

    Padmakumar
    Premier Pathfinder | Tier 7
    Premier Pathfinder | Tier 7
    November 10, 2025

    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.

    Padmakumar
    Zaid Chougle
    Navigator | Tier 3
    Navigator | Tier 3
    November 12, 2025

    @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

    Lets Automate !
    Daiana Grimi
    Navigator | Tier 3
    Navigator | Tier 3
    November 12, 2025

    Object capturing is not working in production, Where as in Dev environment it's working fine both the machine have same configuration 

    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

    Daiana Grimi
    Pathfinder Advocate | Tier 6
    November 15, 2025

    Hello ​@Ajith 9655 please make sure that the production environment has the same screen resolution with your dev environment

    Pathfinder Advocate | Tier 6
    November 15, 2025

    @jahdai.justin  hello, have you checked that if prod and dev environments have the same screen resolution?