Edit History

We found that a hard refresh of local cache on the back-office and front-end cleared the issue for us.

Check in a Incognito window or on a new device if the problem arises, if not then it is a local caching issue.