I have recently had a few items which were downloaded, but not processed for whatever reason (ie: obfuscated name, etc.), by nzbdrone. I manually fixed them and moved them to the Drone Factory where they were then processed correctly. But these items have remained on the Queue list, and still have the “Downloading” circle on the calendar, etc. Is there any way to manually remove them from the Queue?
Remove the item from your download client’s history, that’s where the queue in drone is built from.
That worked, thanks.
I do think it’s suboptimal though, because the download was correctly completed and I might want to keep a record of that in the download client (NZBGet in this case).
It’s the processing that failed, and that’s managed by NZBDrone, surely? Once the processing was “given a helping hand” (ie: in one instance I needed to rename an obfuscated mkv file and then move it to my Drone Factory folder) NZBDrone picked up it’s part of the task, moved and renamed the file into my library and added it correctly to its database.
Should NZBDrone not have realised it had completed it’s part of the task at that point and removed the item from the Queue?
No, because it didn’t import from the same path, it has no idea what you imported via drone factory is the same file that it couldn’t import before (it has no way of knowing).
The solution is to be able to override the import, letting you (the user) choose the proper series/episode(s) to override the error that is preventing it from manually importing, which would let drone handle the import properly. https://trello.com/c/YQ8OI6ml/828-manually-override-failing-cdh-imports which was made because: https://trello.com/c/kr7Jonk4/304-manually-override-drone-factory-imports is specific to drone factory.
OK, I understand now. And thanks for adding the Trello card… I look forward to seeing that implemented.
In the short term - perhaps just a way to manually remove an item from the queue - brutal, I know but just an “x” like in Blacklast to aid my dislike of untidy things? 
Not going to implement a bandaid for a cosmetic issue; you could leave the item in the history and it will eventually fall out of drone’s queue because there are too many newer items in the history of the client.
Harumph! 
Fair enough… Thanks for acknowledging the issue, anyhow.