Sorry to hear that you're still running into this issue! We apologize for the inconvenience, this is currently a known issue and the team is working on a fix. We have no ETA at this time and appreciate the patience. ^BT