@jure_13 I checked with our developer and the problem was on our side. It should be now fixed. Sorry for misleading you. Let me know if it works.