Posted on 21/06/2023 08:56:43
Hi Oleg,
I could not reproduce it either on any of my other solutions. That's why I was thinking this could be a setting somewhere.
Please keep in mind that this is not a fresh project. It's an old project that has been upgraded in time. Therefore something could be off in the database.
The previous version did not experience this behavior, therefore is clearly something introduced by the newer version. And we don't have any customizations apart from the live integration. I have also tested without the Live integration custom code and got the same result.
And the behavior is the same for multiple back-end users. Therefore no potential browser-related cached info cause either.
How should I proceed further?
Thank you,
Adrian