Skip to main content
Solved

When creating a task with Desktop Window Operations (Recorder, IR command, Browser, ... “Recorder unexpectedly disconnected.”

  • September 17, 2025
  • 4 replies
  • 124 views

Forum|alt.badge.img+1

Hi

This notification show up on home screen.

I cannot enter details.

I cannot work with recorder action.

Thanks

Best answer by Padmakumar

Thank you for all answers, after 3 hours it just started working without any extra action 🤷

 

It was a known issue with that specific recorder package, and a fix might be in place now since it got resolved without any action from your end. 

4 replies

Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • September 17, 2025

Hi ​@pawelkt1,

 

Are you getting this error while trying to fetch the availale Browser windows? If so, verify the current version of the Recorder package installed. If the version is 5.0.5, Downgrade the same to version 4.3.2. Re-run the task using the downgraded package.


Forum|alt.badge.img
  • Cadet | Tier 2
  • September 17, 2025

I have the same issue. Version 5.0.5 suddenly stopped working. Version 4.3.2 does work for me, but it's not useful because when I move the bot to production, I get a version error. I need to work with version 5.0.5. I've already tried uninstalling and reinstalling the bot agent, deleting all files and temporary data beforehand. The extension is active, I'm using Google Chrome, and there are no other programs running that could cause conflicts. None of this worked. Any other suggestions?


Forum|alt.badge.img+1
  • Author
  • Cadet | Tier 2
  • September 17, 2025

Thank you for all answers, after 3 hours it just started working without any extra action 🤷

 


Padmakumar
Premier Pathfinder | Tier 7
Forum|alt.badge.img+15
  • Premier Pathfinder | Tier 7
  • Answer
  • September 18, 2025

Thank you for all answers, after 3 hours it just started working without any extra action 🤷

 

It was a known issue with that specific recorder package, and a fix might be in place now since it got resolved without any action from your end.