Skip to main content
Solved

Error starting queued unattended execution after previous job finishes

  • October 1, 2025
  • 1 reply
  • 34 views
bruhfl
Forum|alt.badge.img+1

Hello, everyone. I have a situation with unattended executions: when I have one execution processing and another one waiting, then when the one that is processing finishes and it’s time for the waiting one to start, the following error occurs below. However, after the error, if I go and re-execute it, it processes normally.

 

There is no active user session available for user for the bot to run.Last recorded command try at line number 1.

Best answer by Padmakumar

Hi ​@bruhfl,

 

If your device is configured for single session only (default), and:

  • Job‑1 ends → session is Disconnected.
  • Job‑2 tries to reuse an existing session → fails because CR can’t attach to a disconnected session.

When you manually rerun, you likely have an active RDP session, so it works. So in this case, make sure that the concurrent session is selected.

Vatsy

1 reply

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

Hi ​@bruhfl,

 

If your device is configured for single session only (default), and:

  • Job‑1 ends → session is Disconnected.
  • Job‑2 tries to reuse an existing session → fails because CR can’t attach to a disconnected session.

When you manually rerun, you likely have an active RDP session, so it works. So in this case, make sure that the concurrent session is selected.

Padmakumar
bruhfl
Aaron.Gleason
Terms & ConditionsCookie settingsAccessibility statement