Reservation notifications and Orders do not work consistently

[ihor-chaban]

Several times I noticed the situation when I received the reservation notification but then my orders list was empty.

An example:

When I checked the logs I saw the following error:

ERROR    Create Order Error: (200, b'{"state":"SOLD_OUT"}')

Looks like the notification is being sent when it tries to reserve the bag, not when the bag is actually reserved.

Another thing I observe in such cases - sometimes the order list is not empty, but instead, I see some other monitored bags that obviously can't be reserved at this moment.
So, I assume, when the scanner tries to reserve a bag but fails to do so, it might somehow mess up the failed reservation with others and display invalid information.

An example:

The notification says the bag was reserved, but it's not there. Instead, I see two other orders which are definitely not reserved at the moment.

I think both issues have the same root - incorrect handling of failed reservations.
Unfortunately, debug was not enabled so I don't have relevant logs for such cases to help investigate.
Nothing else useful appears in logs with the default logging level.

[Der-Henning]

Hi @ihor-chaban.
You are totally right. The notification is sent every time the scanner tries to reserve the item, even if it is unavailable. This behavior is not intended and will be fixed in the next release.
Thank you for reporting the issue.

[ihor-chaban]

Thanks @Der-Henning.

Do you know why the second issue might happen also (two other bags are listed in orders instead of the correct one)?