@Awers1 Hello, I tested the behavior on the same location and it did not occur. However, this issue may appear from time to time, due to logic on our backend.

We are currently preparing a release, which will fix this issue.