@n1kk0 I did a bit of sleuthing (pestering our engineers) and it looks like a fix for this bug was pushed into production TODAY! Can you take a look and see if you’re still experiencing this error?
1 Like
@n1kk0 I did a bit of sleuthing (pestering our engineers) and it looks like a fix for this bug was pushed into production TODAY! Can you take a look and see if you’re still experiencing this error?