There may be several reasons a task is not starting. Verify the following below.
1. Task is not within its defined working hours
- The task is set to start within its working hours. It may appear correct, verify that the shifts inside the working hour does include the current time
2. Resource group contains available resources
3. There are Planned Downtime defined for the resources or tasks
4. Licenses have been assigned to RPA Supervisor
- There are available Licenses to start the process. If all licenses are in use, the task will stay Pending until a license is available, or RPAS will decide to stop another task in order to start the Pending one.
5. Underperformance Events may be blocking your task or resource.
6. Blue Prism installs: Resources are logged out and you are not using Automatic Windows Login
- The resource needs to be in the Idle state in Blue Prism if Automatic Windows Login is not enabled in RPAS.
- If Automatic Windows Login is enabled and the resource is in the Logged Out state in Blue Prism, be sure a credential is defined on the task / resource for it to log in.
7. Other tasks may have higher prioritization, and this task may be pending until it is prioritized.
8. Credentials have not been set for the task, or the resource it will be using.
Applies if you are using Automatic Windows Login and the task is attempting to use a logged-out machine but is not configured with a credential to use.
9. Parallel session has not been restricted too much
Verify that your tasks and resource groups (and credentials) are not configured to be restricted on their parallel session limit.
10. Resource Pools/Groups in use in RPA Solution
RPA Supervisor needs direct control of resources so any resources assigned to work with RPA Supervisor cannot be in a pool/group in the base RPA Solution.