Open Daniel-Mietchen opened 4 years ago
That's due to the maxlag parameter; the service is waiting until it drops down and edits can start up again. See pull request #107. This started happening once the WDQS lag was added in to maxlag on Wikidata.
OK. Then it would make sense to inform the user about this, perhaps with a link to the relevant Grafana board. Otherwise, these cases of waiting are hard to distinguish from those when the tool is stalled, e.g. as per #111 .
I am certain there are no conditions under which it actually "stalls". The batch process may end prematurely of course, in which case you should see a link to restart the batch, at least on the main batches page. Maybe that link should be somewhere else?
all that said, we should have some way of reporting that maxlag is causing delays...
e.g. see the first two timestamps in https://tools.wmflabs.org/author-disambiguator/batches_oauth.php?id=e4eb4b