Not all processes are starting via schedules

[SachaHutton]

Only up until recently, some of our processes (not all of them) fail to start via schedule, they remain in a pending state until manually started.
I checked the schedule logs and found this

Task: XXXXX - Session creation failed on resource 'SERVER1': Failed to create session on SERVER1- No reply from Resource PC

I've also found that if that above error appears for 1 process and another is kicked off straight after, I see these errors

Task: XXXXX - Session creation failed on resource 'SERVER1': SERVER1is too busy to run that process.

Has anyone ever come across this before?

[expertcr]

Well, you have two different errors here:

• Task: XXXXX - Session creation failed on resource 'SERVER1': Failed to create a session on SERVER1- No reply from Resource PC
  • This is because the RR is losing connection or timeout. You will need to review why this is happening with your network team. Remember that BP needs a good connection with the RR; having a slow ping reply like more than 5 seconds is not good.
• Task: XXXXX - Session creation failed on resource 'SERVER1': SERVER1is too busy to run that process.
  • This RR may have other processes running and need to wait until it is free. Also, if you create a Resource Pool, we have the following KB Article "How do I fix error "Resource Pool is too busy to run that process." when assigning tasks to Resources in the pool."

If you keep having issues, please get in touch with our support team by creating a ticket so we have one of our engineers work with you.