This should be fixed now on Cloud ![]()
It looks like the fix will ship to self hosted accounts on edge release 3.68.
Let us know if you're still seeing anything unexpected
This should be fixed now on Cloud ![]()
It looks like the fix will ship to self hosted accounts on edge release 3.68.
Let us know if you're still seeing anything unexpected