Henare Degan

The problematic PlanningAlerts ones have their `last_run` marked as queued but they're not in the actual queue. Many of these are "queued" 6 days ago.

They're not isolated: ``` Run.where(finished_at: nil, started_at: nil).where('queued_at IS NOT NULL').count => 131 ```

This: `Run.where(finished_at: nil, started_at: nil).where('queued_at IS NOT NULL').each { |r| RunWorker.perform_async(r.id) }` Seems to have cleared those ones that were previously sitting at the bottom of the PlanningAlerts list.

We have two issues here. The issue I reported initially is different to the one I subsequently worked on above. The initially reported one was where there was a stopped...

@tmtmtmtm you were spot on about guessing what the problem was. I've manually fixed these. I'm still not sure what the long term fix for this is.

Yeah I _think_ we need [something here](https://github.com/openaustralia/morph/blob/master/lib/morph/runner.rb#L144-L159) that handles this case but I'm just not sure _what_, yet :wink: :thought_balloon:

@katkad I've kicked off the stuck run and it's trying to finish now. If it's still a problem, can you please post a message in the help forum? https://help.morph.io/ [Update:...

Of late there's been a build up of scrapers sitting on this page: https://morph.io/scrapers/running with no corresponding running job in Sidekiq. These scrapers can never finish and never be stopped...

@Charrod my last comment above is still the latest on this issue :( It would be so good to get a fix in for this as it continues to affect...

@Charrod if you can't stop your scraper it's a sure sign of this bug and not your scraper. Maybe you'd like to have a go at fixing this issue or...