No, it’s not a front office robot - it takes an excel file from a predefined location, interprets it’s content (it’s a collection of free text task descriptions) and saves it to a different location. Then waits for a human approved list in a predefined folder. It may sound “weird”, but these are process requirements that are non-negotiable.
This is running on console sessions, RDP rights are not granted at all. Starting from tray is not an option, as humans don’t have access to the servers robots are running on and it starts in the middle of the night anyway, so there will be noone to trigger it anyway.
Yes for the second part - it’s a fixed schedule with some leeway, but sometimes authorization takes longer than expected and the new job goes to pending.
We really can’t change much with the settings, as this is a highly controlled environment and as far as this issue goes, nothing will be changed without a couple of months of negotiations (I’m dead serious).
The only issue I’m having is that the job that is Pending sends a start command too soon - 15s after previous one finishes. Since by default if a robot started the session it will logout at the end, it’s a very low time window for the server to free up all resources (especially if the next job uses the same user).