Hi @kalishane_eg .
I’m not sure if it’s the exact same issue, but it was fixed in the v36.20 update. With the v37.00 update this time, it has reverted to its previous state.
1 Like
Hi @kalishane_eg .
I’m not sure if it’s the exact same issue, but it was fixed in the v36.20 update. With the v37.00 update this time, it has reverted to its previous state.