When robot was offline the user could schedule missions but missions would not appear in mission queue.
When robot had connection issues (isarConnected=false), the user could schedule missions, the missions would appear in queue, but the missions would not run even if isar connection was re-established.
After this PR:
The user will not be able to schedule mission if the robot is offline or has connection issues. They will get an error banner with an explanation to the problem.
:bell: Changes in database folder detected :bell:
Do these changes require adding new migrations? :thinking: In that case follow these steps.
If you are uncertain, ask a database admin on the team :smile:
Will close one of the points in #1592.
Prior to this PR:
When robot was offline the user could schedule missions but missions would not appear in mission queue.
When robot had connection issues (isarConnected=false), the user could schedule missions, the missions would appear in queue, but the missions would not run even if isar connection was re-established.
After this PR: