Komf won't update metadata automatically. Need to manually trigger identify/auto-identify to work.

[jj47336]

Good day, I have just installed Komf on my Kavita server about a week ago and I've noticed that it's not doing anything unless I manually trigger identify/auto-identify on a series. I've installed it via the Firefox extension and here are my settings:

Am I missing something? It works fine if it's manually triggered...

[soufflenote]

Same here, seeing the exact same issue trying to connect to the latest version of Kavita. The connection is recognized as okay in the browser extension and I get a 200 response on the terminal but no jobs are created.

[hstraten]

I only see this happening when adding a new series, updating an existing one triggers the job as usual. Same for you guys?
Seen this behaviour since Kavita v0.8.9

[soufflenote]

Yeah same here! I just tested it out by moving an item from my library in an existing series out, rescanning, then back in and scanning. That got processed just fine, so it seems to only happen when a new series is added. I enabled debug logs and added a new book, and once more saw nothing; however, I do see a couple dozen INVOCATION messages going through before the 200 OK response from the server, not sure if that's normal. Snippet of it here since the INVOCATION messages go on for a while but don't seem significantly different.

17:48:21.603 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.610 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.635 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.638 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.662 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.665 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.680 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.728 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.728 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.728 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.728 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.731 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.740 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.741 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type INVOCATION. 17:48:21.742 [OkHttp http://localhost:5000/...] INFO http.logging -- --> GET http://localhost:5000/api/series/volume?volumeId=8396 17:48:21.768 [OkHttp http://localhost:5000/...] INFO http.logging -- <-- 200 OK http://localhost:5000/api/series/volume?volumeId=8396 (25ms, unknown-length body) 17:48:26.919 [Timer-73] DEBUG com.microsoft.signalr.HubConnection -- Sending PING message. 17:48:27.247 [OkHttp http://localhost:5000/...] DEBUG com.microsoft.signalr.HubConnection -- Received message of type PING.

Aaaaaand nothing happens after that, just the usual ping message loop.