Hi Team, i am trying to generate reports of test execution from all the folders in the tenant and send email to others and upload the file to storage bucket. But i dont have 365 connector and i have built smtp mail in workflow and published to cloud and calling that workflow in the agent when my other colleague is running it there is no error and mail is sent but when i am trying to run i am getting this Execution error: Cannot start process for tool ‘Agents’: Foreground job requires an unattended robot to be defined on your user this error can any one help? also i am not able to upload the storage bucket saying file dont exist.
Hi @Madhups,
I think the UiPath user account is not mapped to an Unattended Robot or does not have the required unattended execution permissions. You can ask the UiPath Administrator to verify the unattended robot setup, machine allocation, and execution permissions in Orchestrator.
For the storage bucket upload issue, the workflow cannot find the report file at the specified path. Verify that the report is generated successfully before the upload step, use the correct full file path, and make sure the file exists on the machine where the cloud process is running. If the process runs in the cloud, use a shared/storage location accessible to the robot instead of a local path.
Hi @Madhups,
As per my understanding I see there are two issues here which has to be fixed.
Issue 1 - Foreground job issue (unattended robot error)
This is a per-user config, not a per-tenant one, so your colleague being fine doesn’t mean you are.
- Go to Orchestrator → Tenant → Manage Access → open your user → confirm “Allow to be Automation User” role is assigned, with a Windows/local credential set (domain\username + password) for unattended execution.
- Go to your Tenant → Machines → make sure a Machine Template exists that your user is mapped to, and that it has an unattended license allocated.
Issue 2 – Storage bucket “file doesn’t exist”
- If the process job never actually completed due to Issue 1, the report file was never generated, so the Upload activity correctly reports it missing. Fix the Issue 1 first, then retest.
I hope this helps!
Happy Auotmation!
Hi @Madhups
adding to Prashanth’s answer, one thing worth checking is why that job runs as foreground at all. Foreground needs an interactive session, and thats what forces the unattended robot with windows credentials
if that process just generates a report and uploads it to a bucket, with no clicking on screens, you can switch it to background in the project settings and republish. Background jobs dont need a machine with credentials, so issue 1 goes away without involving IT
if it does use UI automation somewhere, then Prashanth’s steps are the way
hope this helps you as well 