Login to the VM timesout when starting a job - Robotiq

Answered

Hi all,

we’ve encountered an unusual situation with job execution for a schedule that has executions spaced 10 minutes apart.
The initial job (Selenium) is ran but doesn’t manage to find an active session in time and ends in error.
The schedule has 3 retries set up but they all also end in error for the same reason.

The next execution logs in immediately and runs successfuly.

The next execution after the successful one just starts the cycle all over again – job goes to error because of a login timeout (no active session found), retries fail as well, and the next scheduled execution minutes later executes successfully. It just repeats.

When we try to run the process in attended mode on the VM it’s starts and runs normally

Any ideas?

Tnx

Infrastructure and Administration job error login Selenium vm Timeout

Lac asked 3 weeks ago

You must login to post comments

Answers (4)

Best Answer

That’s the exact issue – the Selenium MSEdge closing using Taskkill

When MSEdge is closed normally those files you’ve shown are removed from the Temp folder.
When MSedge is killed that part of the closure doesn’t run and the files remain.
The process runs many times per day and the files just pile up and slow down the login to the VM when te folder gets larger.

You need to either use the Close Selenium Step and the files will not remain after closing the browser or control the folder size by some other means so it doesn’t get to large and affect login times.

Petra Matijevic answered 2 weeks ago

You must login to post comments

Hi,

Have you checked the %appdata% \Local\Temp folder on the VM?
It could cause the long login times when it’s grows in size or file count?

Hope this helps

Petra Matijevic answered 3 weeks ago

You must login to post comments

We’ve checked the %appdata% \Local\Temp and it was huge for some reason – over 600 thousand files. After a little research on the matter that causes the file scan that happens upon login to drag for a long time and really slows up the process of logging into the machine.

When we emptied the folder the login times droped to normal, no issues and the cycle doesn’t repeat as described anymore.

Thank you for your help

We just need to identify why the folder is filling up so much. It’s not happening on other VM’s running other processes.

I’ve noticed repeated edge, msedge and scoped folders

edge_BITS_43644_60900758	14.10.2025. 13:23	File folder
edge_BITS_45092_1089299814	14.10.2025. 13:33	File folder
edge_BITS_45352_359162764	13.10.2025. 16:53	File folder
edge_BITS_46476_1589398553	13.10.2025. 16:03	File folder
FF60943E-311F-4A01-B2D3-9A38FC59C63B	4.10.2025. 10:01	File folder
ListSync	26.9.2025. 13:00	File folder
msedge_url_fetcher_844_1718295639	23.9.2025. 7:12	File folder
msedge_url_fetcher_844_1780445893	23.9.2025. 7:12	File folder
msedge_url_fetcher_920_1250807425	19.9.2025. 13:11	File folder
msedge_url_fetcher_920_1636114792	19.9.2025. 13:11	File folder
msedge_url_fetcher_1020_1236205709	19.9.2025. 7:42	File folder
msedge_url_fetcher_1020_1988816624	19.9.2025. 7:42	File folder
scoped_dir43168_520431314	13.10.2025. 13:33	File folder
scoped_dir43168_1779004397	13.10.2025. 13:32	File folder
scoped_dir43264_220450336	11.10.2025. 13:23	File folder
scoped_dir43264_563485574	11.10.2025. 13:22	File folder
scoped_dir43268_286482462	11.10.2025. 11:33	File folder
scoped_dir43268_1442718022	11.10.2025. 11:31	File folder

And the process uses Selenium with Edge as the browser.

For execution reasons we are using Taskkill to close it instead of the Close Selenium Step

Don’t know why that would cause an issue as it was done previously on different occasions.

Lac answered 2 weeks ago

You must login to post comments

😊 Thanks, didn’t think of that

Since we couldn’t remove the taskkill a scheduled task was set up on the VM to run on every robot login that empties the Temp folder.

After running the schedule several times as a test there are no files anymore when loging in so in the long term they can’t be a problem anymore.