Or do we need to try catch everything to avoid this?
We are working on reply on your similar question in post here.
I have a question if this problem is fixed
In OSS the mentioned issue was resolved and merged and is included in OSS server versions 1.17.x.
For Cloud please ask this question in your company slack and we will check with server team to make sure we give you right right info.