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

Missions in the queue are never started after ISAR reconnects #1685

Closed
andchiind opened this issue Jul 23, 2024 · 0 comments · Fixed by #1691
Closed

Missions in the queue are never started after ISAR reconnects #1685

andchiind opened this issue Jul 23, 2024 · 0 comments · Fixed by #1691
Labels
backend Backend related functionality bug Something isn't working

Comments

@andchiind
Copy link
Contributor

Describe the bug
If ISAR shuts down while missions are being run, once it restarts the remaining missions in the queue are newer started.

To Reproduce
Restart ISAR while running missions

Expected behavior
Once ISAR restarts and becomes available, the next mission in the queue should be started

Screenshots
image
@andchiind andchiind added bug Something isn't working backend Backend related functionality labels Jul 23, 2024
@andchiind andchiind changed the title Missions in the queue are newer started after ISAR reconnects Missions in the queue are never started after ISAR reconnects Jul 24, 2024
@andchiind andchiind mentioned this issue Jul 25, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
backend Backend related functionality bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Trigger robot available when robot comes online andchiind/flotilla
1 participant
@andchiind