The Komga integration is logging multiple duplicate "Completed" entries for the same comic/book, all timestamped on the same day, instead of recognizing that the item was already marked complete.
Steps to reproduce:
Set up the Komga integration (Base URL, API Key) with Minimum progress = 2, Maximum progress = 95.
Read a comic in Komga to completion (progress crosses 95%).
Let the integration sync run (whether on schedule or triggered) multiple times.
Check the item's History tab in Ryot.
Expected behavior:
One "Completed" entry should be recorded per actual read.
Actual behavior:
Media detail pages show an inflated "seen" count — e.g. "Seen 36
times" for a comic I only read once. The History tab shows repeated Completed entries with identical Started/Ended/Updated timestamps, all from the same day.
Environment:
Ryot connected to a self-hosted Komga instance
Integration settings: Minimum progress 2, Maximum progress 95, Sync to Owned collection unchecked, Pause integration unchecked
The Komga integration is logging multiple duplicate "Completed" entries for the same comic/book, all timestamped on the same day, instead of recognizing that the item was already marked complete.
Steps to reproduce:
Set up the Komga integration (Base URL, API Key) with Minimum progress = 2, Maximum progress = 95.
Read a comic in Komga to completion (progress crosses 95%).
Let the integration sync run (whether on schedule or triggered) multiple times.
Check the item's History tab in Ryot.
Expected behavior:
One "Completed" entry should be recorded per actual read.
Actual behavior:
Media detail pages show an inflated "seen" count — e.g. "Seen 36
times" for a comic I only read once. The History tab shows repeated Completed entries with identical Started/Ended/Updated timestamps, all from the same day.
Environment:
Ryot connected to a self-hosted Komga instance
Integration settings: Minimum progress 2, Maximum progress 95, Sync to Owned collection unchecked, Pause integration unchecked