It's been awhile since I've looked at that code. When I worked on it it was to have the stopped status appear when someone manually presses the "stop" button, I thought I added it just for that, but maybe it existed for something else as well. So, ideally, the status doesn't mean to indicate that the query failed or otherwise couldn't run, just that it was stopped while it was running by the user. Are you seeing your queries end with this status without pressing the stop button?

@rook Yes, I did not press the stop button for any of the queries that were stopped and it only displays the above two lines and not any further info like some error code. Other example: https://quarry.wmcloud.org/query/86864

Please prevent queries from getting stopped. One went through but the other still gets stopped all the time.

Seems like much less or no issues now. In any case, please add some info when queries are stopped.

It is possible that you were encountering the three hour time limit for analytics searches. If there was some lag it could have increased your query time from what looks like an hour to later. I'm unsure of how additional data could be provided, though it may be possible. Likely though it is easier to check https://replag.toolforge.org/ for lag which if there was much would suggest long running queries may not complete.