@pooreboy sorry for the late response. We already have an internal issue tracking this. This is a backend issue that we’ve been investigating for some time. Hopefully once this is resolved it’ll just work on whatever client/release you’re on 
.
This thread is linked in our issue, so once it’s resolved I’ll update the thread. Sorry for the frustration and inconvenience this has caused but thank you for your patience. 
