Hey @doronzamir, and @majustice Welcome to the community!
We’ve had a few Local users report this, and it seems to be a bug in the recent version of Chrome. We’ve just created a new topic with a couple of solutions!
Let us know if that solves this for you!