Hey Paul, want to give this another shot? I just tested this on my end and the issue seems to be fixed in version 3.1.1