Quickstatements "Run in Background" not working?
Issue #103
new
I added my latest "run in background" batch yesterday, and it's still sitting there in status "init" with many other "running" batches without any visible activity.
-- Tkarcher
Comments (5)
-
-
Sheri - See Issue #109 here - the problem as far as I can tell is there are some stuck jobs that are eating up the running queue, so it’s been backing up - there are over 40 batches waiting to run, and my most recent one that just started had been waiting about 27 hours.
-
Thank you, Arthur. Good to know.
TBH… it’s amazing it all works & I’m grateful to the folks who keep this up and running.
-
Yeah, it’s pretty impressive, especially the degree to which things are done by volunteers! One way to get a feel for where things are and when you can expect your batch to run is to look at the “Last Batches” page and see what the highest-numbered running batch is (currently 13321). If your batch number is, say, 13341 right now, that means you’re about 20th in line to run.
-
I love this community. Thanks for that helpful bit of info.
- Log in to comment
I’m having the same issue. Has been happening for about a week - maybe more. Sometimes my background processes wait days uninitialized. Other background processes are running fine, but I can’t figure out what might be wrong with my quickstatements that would cause this.