Moving file on import not working

[jmediamanager]

VERSION INFORMATION

Server Version: v5.0.0.43, Channel: Dev, Tag: v5.0.0-dev.43, Commit: d66b282

LOG FILE

2024-12-12.log

DESCRIPTION

Get the follow errors when trying to process files from the drop folder

Warn|Shoko.Server.Renamer.RenameFileService > An error occurred while trying to find a destination for E:\AnimeDrop\[SubsPlease] Amagami-san Chi no Enmusubi - 03 (1080p) [8606E7CF].mkv: The renamer "WebAOMRenamer" could not find a valid destination.

STEPS TO REPRODUCE

1. Setup an Import Folder with type = Drop
2. Setup an Import Folder with type = Destination
3. Scan the Drop Import Folder
4. Verify the error/warning in log
5. Verify that the file has been added to the collection successfully (can see in episode of collection tab)
6. Verify that the folder has NOT been moved to the destination

NOTE - This is a fresh install, and by default the renamer script was empty
I created a new rename script with default WebAOM settings and set it as default

[revam]

@harshithmohan didn't you fix this in a daily? idr which version.

[harshithmohan]

@harshithmohan didn't you fix this in a daily? idr which version.

I did, in 5.0.0.55

[revam]

so @jmediamanager it should be fixed in a newer daily, and in the next stable, so closing this now. also hello. 👋

[harshithmohan]

Just to add, it won't automatically fix it for everyone when they update. It's fixed for new users

[jmediamanager]

@revam hello :)
@harshithmohan if only fixed for new users, does it mean I have to start from scratch?

[revam]

didn't you already fix it by creating a new renamer config and setting said config as the default config to use? @jmediamanager

[jmediamanager]

didn't you already fix it by creating a new renamer config and setting said config as the default config to use? @jmediamanager

Yup, updated to 5.0.0.86
Created a new renamer after the update and still having the same issue. Attaching log if relevant
2024-12-13.log

And just to clarify, creating a new config didn't fix it before the update either

[jmediamanager]

@revam @harshithmohan FYI - I traced through the code myself, and found that it was failing on the disk space checks
So I set the setting for SkipDiskSpaceChecks to true, and now the moving works fine
Although it renames the file now, even though I have "Rename on import" disabled, but I can live with that

[harshithmohan]

I thought we were talking about the script being empty. That was fixed 😅

[jmediamanager]

Oh well yes I guess the script was fixed then :)
But not the issue I raised

[revam]

@revam @harshithmohan FYI - I traced through the code myself, and found that it was failing on the disk space checks So I set the setting for SkipDiskSpaceChecks to true, and now the moving works fine Although it renames the file now, even though I have "Rename on import" disabled, but I can live with that

Was it during an automatic rename/move job or in the renamer utility in the Web UI that it potentially wasn't respecting the "Rename on Import" setting?

[jmediamanager]

During the import process (i.e. press "rescan folder" from the Web UI)