Open prasm313 opened 8 months ago
Could updating the robot status in OnIsarRobotHeartbeat if the robot is not enabled solve this problem? The only thing is that as of now the robot status is not contained in the heartbeat.
Blocked waiting on improved communication between ISAR and Flotilla. This includes some new states in ISAR. It also means we can rely on one of the messages instead of the combined status message.
This issue has automatically been marked as stale as there has been no activity for 60 days.
Describe the improvement you would like to see If the broker goes down and is restarted, the robots has "offline" as their status. If the robot is available or busy when the broker restarts this should be visible in Flotilla.
How will this change existing functionality? Robots will not be stuck in offline. Will not be necessary to manually set status as Available through swagger. The users would not need to contact us if the broker has restarted.
How will this improvement affect the current Threat Model? N/A