Sorry for the inconvenience. In this specific case, it was b + c. You were hitting a bug, one of our services was broken and our detection mechanism had a gap.
The fix has been deployed. Let me know if you still have the issue.
1 Like