2 Replies
hey, @magicseth, we see the error on our side. @sshader is digging into it.
Does this happen consistently, or does it go away on refresh? Our current theory is that this should only happen in a somewhat rare case when we're retrying a mutation (but is definitely a bug on our side that we're looking into fixing).
Update: we believe we have a fix for the bug, and will push it out soon.