Receiving simple error only when running "Analyze Files" on a library

[AndrewHoover]

What happened?

When I try to run an "Analyze Files" call from the UI on a library, I see a red box in the lower right of the screen that says "Something unexpected went wrong" and I do not see any further indicators either in the UI or in the logs of what the error was or if analysis continued beyond the error.

I bumped the log level to trace and tried it again but didn't see anything more than before in the logs. Only the call to run the analyze process but nothing afterward.

[Kavita] [2025-07-30 08:48:29.174 -05:00 76] [Information] Serilog.AspNetCore.RequestLoggingMiddleware HTTP POST /api/library/analyze?libraryId=2 responded 200 in 0.9388 ms

What did you expect?

I am new to Kavita so I am not sure what to expect but if the process is similar to onboarding a library then I would have expected the status indicator at the top right of the window to show activity and if there were issues then something recorded in the log and/or an entry shown in the media issues section of the admin panel.

Kavita Version Number - If you don't see your version number listed, please update Kavita and see if your issue still persists.

0.8.7 - Stable

What operating system is Kavita being hosted from?

Docker (Other)

If the issue is being seen on Desktop, what OS are you running where you see the issue?

None

If the issue is being seen in the UI, what browsers are you seeing the problem on?

Firefox

If the issue is being seen on Mobile, what OS are you running where you see the issue?

None

If the issue is being seen on the Mobile UI, what browsers are you seeing the problem on?

No response

Relevant log output

[Kavita] [2025-07-30 08:48:29.174 -05:00  76] [Information] Serilog.AspNetCore.RequestLoggingMiddleware HTTP POST /api/library/analyze?libraryId=2 responded 200 in 0.9388 ms

Additional Notes

I am running Kavita in unraid installed using the linuxserver repository from CA.

[majora2007]

Just fyi, analyze files doesn't matter to new users. It can likely be removed as it was only necessary when Kavita added file extension and size information to the db.

I think you are looking to use Scan instead.

[AndrewHoover]

Ok, that's good. So this function will be depreciated in a future release?

[majora2007]

Yes exactly. I have to check our stats db to ensure most users are above the migration point then I can remove it safely will less hinderance on users upgrading from over a year ago (we got a lot of users on old builds unfortunately).