Closed macwinnie closed 1 year ago
According to my research, this issue is caused by comparing the planned departure/arrival times instead of the real-time data in this function. A dirty fix would be to increase the tolerance (currently at 10 minutes, maybe push it up to 60) but this would defeat the purpose of this function. To fix this issue in a nice way, the real-time data is needed in this function. As I'm only beginning to look through the code, I have no idea how to get the data there, maybe someone from the team can help by hitting me up with the right information or just fixing this real quick, as this shouldn't be the greatest hassle.
Our backend can now force checkins. This can already be used via the API. The frontend has not yet implemented this possibility.
Describe the bug
Today ICE 526 was late (+65 when leaving MH) and could be reached by ICE 789.
Checkin was not permitted.
Expected behavior Checkin should have been permitted.
Screenshots
Smartphone (please complete the following information):