If a Job that is running is replaced with a new file(for example, the file is upgraded), Encodarr will still copy the completed file even though it is not relevant.
The problem is detecting this kind of change. A hash could be computed when the Job is dispatched/generated and checked again when the file is ready to be copied back. This only works for files named the same, but some file existence checks could supplement that as well.
Whatever the solution, it probably should be an option for the user.
If a Job that is running is replaced with a new file(for example, the file is upgraded), Encodarr will still copy the completed file even though it is not relevant.
The problem is detecting this kind of change. A hash could be computed when the Job is dispatched/generated and checked again when the file is ready to be copied back. This only works for files named the same, but some file existence checks could supplement that as well.
Whatever the solution, it probably should be an option for the user.