We are facing below issues while using Resource Pool.
Requirement here is to start the Login process on all the Resources inside the Pool.
Issue: When this Schedule is executed, we observed that sometimes session is created only on 3 Resources out of 4. Even when all the Resources are idle. The error message seen in the Recent Activity report says “Session creation failed on resource ‘RobotsPool’: RobotsPool is too busy to run that process.”
Requirement here is to start the Login process on all the Resources inside the Pool.
Issue: When this Schedule is executed, we observed that sometimes sessions are created for all 4 Resources inside the pool, but one of the session remains in “Pending” state. It is not executed at all. It then needs manual intervention.
Issue: Suppose a process, scheduled on the Resource pool somehow runs into a “Warning” state, then Schedule 2 and rest of the schedules executed on the Resource Pool fail to execute. Even when there are idle Resources available in the Pool. The error message seen in the Recent Activity report says “Session creation failed on resource ‘RobotsPool’: RobotsPool is too busy to run that process.”
If anyone has faced any or all of the above issues, please provide any pointers on how to make sure these issues do not arise.
Thanks,
Anish
- Session not getting created on one of the Resources in the pool
Requirement here is to start the Login process on all the Resources inside the Pool.
Issue: When this Schedule is executed, we observed that sometimes session is created only on 3 Resources out of 4. Even when all the Resources are idle. The error message seen in the Recent Activity report says “Session creation failed on resource ‘RobotsPool’: RobotsPool is too busy to run that process.”
- Session remains in “Pending” state for one of the Resources in the pool
Requirement here is to start the Login process on all the Resources inside the Pool.
Issue: When this Schedule is executed, we observed that sometimes sessions are created for all 4 Resources inside the pool, but one of the session remains in “Pending” state. It is not executed at all. It then needs manual intervention.
- If a Process running on a Resource from the Resource Pool is in Warning State, subsequent Schedules on the Resource Pool fail to execute
Issue: Suppose a process, scheduled on the Resource pool somehow runs into a “Warning” state, then Schedule 2 and rest of the schedules executed on the Resource Pool fail to execute. Even when there are idle Resources available in the Pool. The error message seen in the Recent Activity report says “Session creation failed on resource ‘RobotsPool’: RobotsPool is too busy to run that process.”
If anyone has faced any or all of the above issues, please provide any pointers on how to make sure these issues do not arise.
Thanks,
Anish