Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Trigger missed #56

Open
andriussi opened this issue Dec 9, 2020 · 1 comment
Open

Trigger missed #56

andriussi opened this issue Dec 9, 2020 · 1 comment

Comments

@andriussi
Copy link

andriussi commented Dec 9, 2020 •
edited
Loading

Hi
I just encountered orchestrator skipping one scheduled robot. After looking at the console I noticed, that it did a restart at 10:01:02 and the robot was supposed to run at 10:01:00. However in this case i guess the 10:01:00 happened while the orchestrator was restarting.

I think it would be useful to have a check that there are no robots scheduled in the next 5 mins or so before doing the restart.

Console:
image

Schedule:
image

Executions:
image
@Ghitafjorback
Copy link

Did you manage to find a solution for this issue? We have SEVERAL of these happen. :(

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Ghitafjorback @andriussi