@iammikek 5.3 could very well be the culprit; we have not yet tested on that version so I wouldn’t be surprised if there are problems