Test Execution in Pending State - Not getting started

Help Orchestrator
,
1

Hello All,

I’m trying to execute a test case from orchestrator. But the execution is not getting started. It remains in Pending state forever. I have attached the screenshots of my set up here.

Access:

image
image1484×227 24.5 KB

Machine:

image
image1491×197 21.2 KB

Execution Target:

image
image1430×741 30.8 KB

Execution:

image
image999×187 20.2 KB

UiPath Assistant:

image
image629×511 22.2 KB

Requesting for your help on this.

Thank you.

2

Hey @aqeel.ngl
Looking at your screenshots, it would be good to make sure that on the Machine Template assigned in Orchestrator, the proper Testing runtime license is allocated. Please go to Machines → select your Template → Edit → and in the “Runtime Licenses” section, check if you have assigned Testing to 1. If this is not configured, your test execution will stay in a Pending state, because Orchestrator won’t know that it can use this machine for test runs.

The image displays a software interface for configuring machine templates, specifying runtime licenses for production and testing, with inputs for template name, description, process type, and compatibility. (Captioned by AI)
The image displays a software interface for configuring machine templates, specifying runtime licenses for production and testing, with inputs for template name, description, process type, and compatibility. (Captioned by AI)1597×676 50.9 KB

3

Hi @pikorpa

Thank you for the response.

I already have a machine template with Testing Run Time assigned to 1.

image
image1410×733 58.9 KB

But the execution is still in pending state. Can you please have a look?

4

Hey @aqeel.ngl
I can see that your Account is selected, but there are no credentials defined (it says “no credentials defined” next to your name).

The image shows a software interface for selecting an execution target with dropdowns for runtime type and account, and input fields for machine and hostname, alongside 'Cancel' and 'Execute' buttons. (Captioned by AI)
The image shows a software interface for selecting an execution target with dropdowns for runtime type and account, and input fields for machine and hostname, alongside 'Cancel' and 'Execute' buttons. (Captioned by AI)1430×741 30.8 KB

In order to run unattended jobs (like Testing RunTime or scheduled tests), Orchestrator needs to know how to log in to the machine automatically.
Without credentials (username + password), the robot cannot establish a session, and that’s why your execution is stuck in Pending state.

Please go to Orchestrator > Tenant > Manage Access > [your robot name] > Edit and define the Windows credentials for your user.

A user interface displays options for managing accounts, including "Robot account," "Allow to be Automation User," "Direct assignment," with a dropdown menu offering "Edit," "Check access," and "Unassign" options. (Captioned by AI)
A user interface displays options for managing accounts, including "Robot account," "Allow to be Automation User," "Direct assignment," with a dropdown menu offering "Edit," "Check access," and "Unassign" options. (Captioned by AI)2303×227 13.5 KB

Make sure you provide the correct Domain\Username and Password that match your machine.
The image shows a user interface where custom Windows credentials are being configured for a robot account, with options for enterprise robot setup, domain username, credential store, password, and credential type. (Captioned by AI)
The image shows a user interface where custom Windows credentials are being configured for a robot account, with options for enterprise robot setup, domain username, credential store, password, and credential type. (Captioned by AI)1449×1045 103 KB

After saving credentials, your unattended jobs should start properly.

5

Hi @pikorpa

I have provided the credentials as instructed. But still the issue exists.

image
image710×678 33.7 KB

image
image1407×729 29.3 KB

image
image896×173 13 KB

Can you please advise?

6

Hi @aqeel.ngl

Could you please verify that the Robot account and Machine have been correctly assigned to the appropriate folder?

The image shows a software interface with a context menu for folder management, highlighting options to manage folder access and assign machines. (Captioned by AI)
The image shows a software interface with a context menu for folder management, highlighting options to manage folder access and assign machines. (Captioned by AI)357×388 17.7 KB

7

@aqeel.ngl
Please check if you assign your robot to the correct folder

The image shows a settings screen for managing access in a software application, highlighting the "Assign account/group/external app" button, with various roles listed in a table including administrators and automation users. (Captioned by AI)
The image shows a settings screen for managing access in a software application, highlighting the "Assign account/group/external app" button, with various roles listed in a table including administrators and automation users. (Captioned by AI)2555×383 63.9 KB

The image shows an interface for assigning an account to a shared folder, with options to select an existing account, create a new robot account, and assign roles, such as "Automation User". (Captioned by AI)
The image shows an interface for assigning an account to a shared folder, with options to select an existing account, create a new robot account, and assign roles, such as "Automation User". (Captioned by AI)1326×665 34 KB

8

@pikorpa

I have already added the user to the folder with Robot type as Attended and Unattended. Please find the screenshot.

image
image1901×436 60.6 KB

9

Hi @Pankaj_21

I have already added the user to the folder with attended and unattended robot type.

image
image1906×417 66.6 KB

10

Hi @aqeel.ngl

Can you try the following:

  • Delete the existing execution
  • Re-connect the assistant
  • Run the test case
11

@aqeel.ngl

The problem is no credentials are provided for login..

Please go to tenants → mnaage access → edit user → unattended setup and provide credentials there

IMG_8973
IMG_8973828×120 20.1 KB

Cheers

12

Hi @pikorpa @Pankaj_21

The issue is resolved now. The cause of the issue is the Domain\username. The name was auto populated while assigning access. But the auto populated name was incorrect. Later on providing the correct username, its resolved.

The correct domain\username is found using “whoami” command in command prompt.

Thank you for your support.

1 Like
13

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.