Revert files via the GUI/CLI - restored to a different folder
Posted: 13 Jan 2026, 00:23
Hey,
First of all, thank you very much for the sensational programme, your commitment and support.
I have the following request:
You already offer the backup function, which refers to the history. Would it be possible to add an option to the backup menu in the GUI to set the source directory or the new destination directory before the actual backup?
In other words: AMC/Docker Container has detected something incorrect and already renamed it, and I want to manually undo this via the GUI, but it should be restored to a different folder with the original file name.
Why am I making this request?
I let AMC automatically detect and move everything via a container. Sometimes the source files are simply rubbish and something is detected that is not correct. But when I undo it, my automation immediately detects it again and reassigns it incorrectly. This is because it is restored to the watch folder. I deliberately do not have any locks in the watch folder; it should also process files that have already been processed again and again and overwrite my target library (because my new files are always of better quality).
I hope I have explained the context well and that the request is feasible and will also please others and you! If you have a solution to my challenge, I would be happy to accept it.
Many thanks,
Seger
First of all, thank you very much for the sensational programme, your commitment and support.
I have the following request:
You already offer the backup function, which refers to the history. Would it be possible to add an option to the backup menu in the GUI to set the source directory or the new destination directory before the actual backup?
In other words: AMC/Docker Container has detected something incorrect and already renamed it, and I want to manually undo this via the GUI, but it should be restored to a different folder with the original file name.
Why am I making this request?
I let AMC automatically detect and move everything via a container. Sometimes the source files are simply rubbish and something is detected that is not correct. But when I undo it, my automation immediately detects it again and reassigns it incorrectly. This is because it is restored to the watch folder. I deliberately do not have any locks in the watch folder; it should also process files that have already been processed again and again and overwrite my target library (because my new files are always of better quality).
I hope I have explained the context well and that the request is feasible and will also please others and you! If you have a solution to my challenge, I would be happy to accept it.
Many thanks,
Seger