Comment 3 for bug 1867642

Having the STARTED status could help debugging the issue, and it sounds like a simple and non-breaking update, so +1 to that.

On the other hand, it would be nice to hunt for a particular case to investigate and check logs to gather as much information as possible to understand the real issue. I guess the worth in investing time in a work-around without knowing the problem behind depends on how often do we have these and how "undebuggable" this is.