Is it normal to have a blank running job?
Is it discussed here?
I do not see the same on my hub. So, probably not normal?
I fixed it by stopping one rule at a time until I found the guilty one.
Bruce agrees with you. He said "haven't seen before" ...
There will be a way to delete an orphaned job (or any other job, for that matter) in the next release.
The "use with caution" disclaimer applies, of course. Deleting a wrong job is going to break some app/driver functionality.
Would that apply to both scheduled and running jobs? I'd particularly like to use the former.