Currently a failing scheduled query's failures counter will only reset when it's executed again from the scheduler. This means that if the query failed enough times the next execution might be significantly delayed even though it runs properly when triggered by a user.

It might be tricky to update the counter as we don't always pass the query object, a temporary fix is to update the counter when updating latest_query_data_id.