We are getting this error a lot lately. And the main problem is that, while the run is rerun correctly, for a while the run is reported as failed, so our automated tools pick this status and mark the whole run as a failure even though it eventually passes.
Could someone let us know if:
- a) there is some work being done to fix the underlying issue making these runs fail
- b) it would be possible to not mark the run as failed if this condition is detected