Triggers aren't fired at their time

Hi folks,

I have seen that triggers are not launching the processes at the right hour. For example, I have a trigger at 11:00 am and the job starts over 11:15-11:25.

It happens often, but not always. Is somebody facing the same problem?

Orchestrator version: 2020 Enterprise
UiRobot: 20.4.1
Studio: 20.4.1

KR,
Pablo

hi @Pablo_Sanchez,

Is timezone a factor here ?

@Pablo_Sanchez
One thing to check, if there is any previous job running on that machine, does your trigger says pending ?

hi @mukeshkala

No, it shouldn’t be, because most of the processes are executing in their right trigger time.

KR,
Pablo

Hi @Lakshay_Verma,

No, it should be triggered at 11:00 am and we have availables machines. Normally it works fine at 11:00 but other times its triggered at 11:15…20…25… over that times.

The processes should be on pending at least, but their not even triggered.

KR,
Pablo

Well, Why don’t you check Event Logs on machine to see what time bot is triggered.
Go to Event Logs and check Windows logs. If possbile please share your logs.

1 Like

Sorry for spanish version :stuck_out_tongue:

As you can see, the job started at 11:15 when it should be triggered at 11:00 am.

KR,
Pablo

Hey @Pablo_Sanchez

I am talking about windows event logs, Below is SS, you can filter by UiPath and ORchestrator Applciation

1 Like

Hey guys,

it’s solved by itself, i guess it was an Orchestrator Cloud problem or it has to be something like that

KR,
Pablo

3 Likes

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