Hi All. We are working on this issue. I will update as soon as it is resolved.
Thanks for the headsup Saltuk!
The incident is published. You may follow up on the status from this link.
Thanks so much for the workaround! I’ve implemented it and it is now working.
Hopefully it doesn’t take too much to be fixed, so we can roll it back.
We’ll let you know as soon as the official fix is there! Sorry for the inconvenience!
I see this incident is being monitored - just noting I’m still seeing the behavior.
Thanks @elijordan, I have passed this on and it is still being looked into
Probably a duplicate comment, but better more than not enough info
We’re seeing this issue still as well, now also on our prod domain (https://antidote.me) - yesterday we only noticed it while using our development environment from localhost.
The remaining issues were likely due to our proxy cache. We have purged the cache. @eva.csengeri-pap could you confirm if it is working now?
Hey @Saltuk! Yes, thanks a lot, everything seems to be in working order now
@Saltuk same here - the outstanding issue I was hitting does seem to be resolved with the proxy cache clear. Thank you!
@Saltuk Same here. It’s working now.
Thank you very much!
Perfect! Glad to hear that!