topic RE: Process is not picking up by the Scheduler in Product Forum

Process is not picking up by the Scheduler

arghya.b — Tue, 03 Sep 2019 08:57:00 GMT

All the process is not automatically picking up by the scheduler.But if trying to run manually it is running with no error.
Can any one please help on that.

------------------------------
Arghya Bhattacharyya
RPA Developer
Infosys Ltd
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

JerinJose — Tue, 03 Sep 2019 09:12:00 GMT

what is the error that you are getting on recent activity?
Schedules are getting triggered from application server.
1.please check is scheduler is disabled
2.is the runtime resources showing connected to application server

------------------------------
Jerin Jose
RPA Product SME
EY
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

arghya.b — Tue, 03 Sep 2019 09:17:00 GMT

Scheduler are enabled and also the run time resources are online and available.
No error is throwing.
Only the processes are not running by the scheduler.

------------------------------
Arghya Bhattacharyya
RPA Developer
Infosys Ltd
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

JerinJose — Tue, 03 Sep 2019 09:41:00 GMT

there will be schedule logs available in Scheduler>reports>recent activities please check the reason there.

------------------------------
Jerin Jose
RPA Product SME
EY
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

MariusBalukevic — Tue, 03 Sep 2019 09:44:00 GMT

Hi Guys,

I have the same Problem, some Resources are not working. On some resources only login process starting and second process is not running automatically after login. Other resources has 4 schedules to run but not even one is starting automatically.

VERBOSE [2019-08-20 11:21:37Z UTC]- Schedule '02620 II V20249' - Task 'Login':

Not connected to V20249 (b43ac944-27a3-4448-af17-17399afc2e99); State:Connecting; Retries: 10

VERBOSE [2019-08-20 11:21:37Z UTC]- Schedule '02620 II V20249' - Task 'Login':

Failed to connect to V20249: BluePrism.Scheduling.ScheduleException: Resource V20249 : Timed out waiting for valid connection

at BluePrism.AutomateAppCore.ScheduledTask.ConnectToResource(clsResourceConnectionManager manager, ScheduledSession sess)

at BluePrism.AutomateAppCore.

------------------------------
Marius Balukevicius
Platform Engineer
Danske Bank
Europe/London
------------------------------

RE: Process is not picking up by the Scheduler

arghya.b — Tue, 03 Sep 2019 09:56:00 GMT

Server offline is the reason on Termination Reason

------------------------------
Arghya Bhattacharyya
RPA Developer
Infosys Ltd
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

JerinJose — Tue, 03 Sep 2019 10:04:00 GMT

@MariusBalukevic: are you using version 6.2 or 6.3? I had the same issue with this versions and BP service restart was the only remediation.

additional Note: If you are running a process immediately after Login process, scheduler may find the machine as offline (there is a delay is starting resource PC listener after stopping login agent ) and will try it after 5 sec and for 10 times (50 sec in total-this is default config this can be increased from System>scheduler. needs a service restart for changes to take effect)
From version 6.3 you can add a wait time between subsequent tasks in the same schedule try this changes

------------------------------
Jerin Jose
RPA Product SME
EY
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

MariusBalukevic — Tue, 03 Sep 2019 10:09:00 GMT

We were using 6.2 version and we had the same issues, BP support advised us to upgrade to 6.4.2. we did the upgrade all those scheduling issues were gone for few months, but a couple weks ago they apeared again on 6.4.2 version. Any advise regarding this ?

------------------------------
Marius Balukevicius
Platform Engineer
Danske Bank
Europe/London
------------------------------

RE: Process is not picking up by the Scheduler

JerinJose — Tue, 03 Sep 2019 10:11:00 GMT

@Arghya Bhattacharyya please provide the exact error from Blue prism: Looks like there is a network connectivity issue from Application server to runtime resource. resource may show connected in interactive client but may be offline to application server

------------------------------
Jerin Jose
RPA Product SME
EY
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

arghya.b — Tue, 03 Sep 2019 10:16:00 GMT

below is the reason

Termination reason : Task: xxxx threw an exception : Resource YYY is offline - retried 10 times.

------------------------------
Arghya Bhattacharyya
RPA Developer
Infosys Ltd
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

JerinJose — Tue, 03 Sep 2019 10:17:00 GMT

I Never experienced this issues from version 6.4.2 and Higher. ensure the resources reports to application server properly and increase the time of retry or duration between retries.
Also check if the schedules are working after a service restart.

if none of the above works better reach out to BP Support 🙂

------------------------------
Jerin Jose
RPA Product SME
EY
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

MariusBalukevic — Tue, 03 Sep 2019 10:24:00 GMT

We we already have BP support ticket raised, but still no luck. Time of retry and duration between retries increased as per best practises suggested.

regards,
Marius

------------------------------
Marius Balukevicius
Platform Engineer
Danske Bank
Europe/London
------------------------------

RE: Process is not picking up by the Scheduler

JerinJose — Tue, 03 Sep 2019 10:25:00 GMT

resources are reporting "not connected" to application servers. they are reporting connected to interactive client that is the reason why manual triggering works. However for scheduler to work resources should show "Yes-Connected" in Application server do a telnet from application server and see if runtime resources are reachable on port 8181 (if you have a different port configuration use that) Also try changing the mode of resource communication from
register and communicate using machine short name to register using machine short name and communicate using FQDN
you can find the setting in System>Settings

------------------------------
Jerin Jose
RPA Product SME
EY
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

JerinJose — Tue, 03 Sep 2019 10:29:00 GMT

Also try changing the mode of resource communication from
register and communicate using machine short name to register using machine short name and communicate using FQDN
you can find the setting in System>Settings
this helped me tackling machine offline issues in the past (is you infra hosted in cloud? its better to go with FQDN if you are in Azure or any other cloud)

------------------------------
Jerin Jose
RPA Product SME
EY
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

arghya.b — Tue, 03 Sep 2019 11:37:00 GMT

@JerinJose But the Problem is some time the Scheduler is working after restarting the runtime server.If there is any connectivity problem then it should fail every time i think so .Please correct me if i am wrong.

------------------------------
Arghya Bhattacharyya
RPA Developer
Infosys Ltd
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

JerinJose — Tue, 03 Sep 2019 11:55:00 GMT

@Arghya Bhattacharyya I used to have this inconsistent behaviour on resource connectivity and it was resolved by changing to register using machine short name and communicate using FQDN you can also try that. if you are on lower version than 6.4.2 better get upgraded to 6.4.2 or 6.5.1

I had experienced this scheduler issues in 6.2 and 6.3 . 6.4.2 works without failure for me

------------------------------
Jerin Jose
RPA Product SME
EY
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

arghya.b — Wed, 04 Sep 2019 11:45:00 GMT

sure, Thank you jerin i will check that.

------------------------------
Arghya Bhattacharyya
RPA Developer
Infosys Ltd
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

Jatin__Kalra — Wed, 15 Jul 2020 10:41:00 GMT

Hi Jerin,
Could you please help me to know what is significant to make following change:
"Also try changing the mode of resource communication from
register and communicate using machine short name to register using machine short name and communicate using FQDN
you can find the setting in System>Settings"
As mention above.
As our bots are facing termination :
a. Status of Terminated found. Terminating remaining sessions
b. Session creation failed on resource '<Resource Name>': Failed to create session on<Resource Name> - Failed to get effective run mode - Execution Timeout Expired. The timeout period elapsed prior to completion
c. Session creation failed on resource <Resource Name>: Failed to create session on <Resource Name> - ERROR : Execution Timeout Expired. The timeout period elapsed prior to completion of the operation
d. threw an exception: No sessions were successfully created
e. Invalid Session State for session 591fdcae-f541-493f-a185-8bad0d05f10a : All
f. Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
g. A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
h. threw an exception: Resource WINV5EA881 is offline - retried 10 times
Please let me know what steps should we take to resolve this kind of frequent issue and save a machine to terminate a process
Thanks
Jatin Kalra

------------------------------
Jatin Kalra
Assistant Manager
Genpact
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

JerinJose — Wed, 15 Jul 2020 15:21:00 GMT

@Jatin__Kalra
a. Status of Terminated found. Terminating remaining sessions -solution uncheck fail fast on errors in schedule configuration
b. Session creation failed on resource '<Resource Name>': Failed to create session on<Resource Name> - Failed to get effective run mode - Execution Timeout Expired. The timeout period elapsed prior to completion -Solution-check if object references are correct on the process looks like some object references are missing hence failing to calculate effective runmode
c. Session creation failed on resource <Resource Name>: Failed to create session on <Resource Name> - ERROR : Execution Timeout Expired. The timeout period elapsed prior to completion of the operation
d. threw an exception: No sessions were successfully created
e. Invalid Session State for session 591fdcae-f541-493f-a185-8bad0d05f10a : All
f. Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
g. A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The semaphore timeout period has expired.)
h. threw an exception: Resource WINV5EA881 is offline - retried 10 times
errors c-h seems to be related to network connectivity. check if there is any issue with DNS is your Runtime resources IPs Dynamic??

------------------------------
Jerin Jose
RPA Product SME
EY
Asia/Kolkata
------------------------------

RE: Process is not picking up by the Scheduler

Jatin__Kalra — Wed, 15 Jul 2020 15:52:00 GMT

Hi @JerinJose

Thanks for immediate reply.

a. Status of Terminated found. Terminating remaining sessions -solution uncheck fail fast on errors in schedule configuration
According to the statement we trying to stating that if one scheduler having multiple tasks to execute like Task1,2,3...... and if Task 2 get fails due to any error(consecutive 3 system exception, internal exception or might be connection lost) it will mark fail to other successor task also like task 3,4,.....
if fail fast on errors check box is checked.
Make me correct but marking fail fast on errors check box is checked is consider as best practice? What's your take in it ?

b. Session creation failed on resource '<Resource Name>': Failed to create session on<Resource Name> - Failed to get effective run mode - Execution Timeout Expired. The timeout period elapsed prior to completion -Solution-check if object references are correct on the process looks like some object references are missing hence failing to calculate effective runmode

As per the above solution we are trying to state that some Object reference is missing from Process studio. It means Object studio Action is missing or it name get change.
But we are getting this error sometimes.

errors c-h seems to be related to network connectivity. check if there is any issue with DNS is your Runtime resources IPs Dynamic??
Requesting you could you please elaborate it more clearly that would help full to understand.

Thanks
Jatin Kalra

------------------------------
Jatin Kalra
Assistant Manager
Genpact
Asia/Kolkata
------------------------------