[Bug]: File downloads don't register as sucessfull

[TimetravelerDD]

Describe the bug

the bug causes the download queue to fill up

Steps to reproduce

I am archiving a large group and my downloads get "stuck". I says it downloads 5 files or 10 files (whatever is configured in the settings), but the files are actually small and don't make any progress. When I try to pause it shows:

Request Failed
Key: /7362833039/file/toggle-pause-download
File is already downloaded successfully

and the file immediately jumps from "Downloading" to "Completed"

Expected behavior

the app should somehow recognize that the download actually completed or eventually retry if in the download queue for too long

Screenshots

Logs

no relevant logs. it simply shows [2026-01-25 23:13:38] [INFO] Start download file success! ChatId: -100xxxxx82581 MessageId:36xxxxx9760 FileId:10248

Environment

0.3.0

Additional context

No response

[jarvis2f]

8d8e2c5

I tried to fix it, you can try it using the dev image

[TimetravelerDD]

looks very promising! I am seeing logs like this now:

[2026-01-30 18:18:01] [INFO] Start download file success! ChatId: -1001258867564 MessageId:7401897984 FileId:11227
[2026-01-30 18:18:01] [INFO] Start download file success! ChatId: -1001258867564 MessageId:7457472512 FileId:11218
[2026-01-30 18:18:01] [INFO] Start download file success! ChatId: -1001258867564 MessageId:7443841024 FileId:11222
[2026-01-30 18:18:02] [INFO] Start download file success! ChatId: -1001258867564 MessageId:7462715392 FileId:11212
[2026-01-30 18:18:02] [INFO] Start download file success! ChatId: -1001258867564 MessageId:7396655104 FileId:11230
[2026-01-30 18:18:10] [INFO] [9735b671eae2] Reconciliation: File completed but not updated in DB: AQADVbIxG8MUGUl-
[2026-01-30 18:18:10] [INFO] [9735b671eae2] Reconciliation: File completed but not updated in DB: AQADU7IxG8MUGUl-
[2026-01-30 18:18:10] [INFO] [9735b671eae2] Reconciliation: File completed but not updated in DB: AQADyK8xGzgY8Eh-
[2026-01-30 18:18:10] [INFO] [9735b671eae2] Reconciliation: File completed but not updated in DB: AQADcrExG0EjqUh-
[2026-01-30 18:18:11] [INFO] Start download file success! ChatId: -1001258867564 MessageId:7376732160 FileId:11233
[2026-01-30 18:18:11] [INFO] Start download file success! ChatId: -1001258867564 MessageId:7374635008 FileId:11236
[2026-01-30 18:18:11] [INFO] Start download file success! ChatId: -1001258867564 MessageId:7373586432 FileId:11239
[2026-01-30 18:18:11] [INFO] Start download file success! ChatId: -1001258867564 MessageId:7342129152 FileId:11242
[2026-01-30 18:18:40] [INFO] [9735b671eae2] Reconciliation: File completed but not updated in DB: AQADQbExG0EjqUh-
[2026-01-30 18:19:51] [INFO] Start download file success! ChatId: -1001258867564 MessageId:7306477568 FileId:11475
[2026-01-30 18:19:51] [INFO] Start download file success! ChatId: -1001258867564 MessageId:7262437376 FileId:11490
[2026-01-30 18:19:51] [INFO] Start download file success! ChatId: -1001258867564 MessageId:7319060480 FileId:11472

[TimetravelerDD]

for the most part it worked very well and downloaded the bulk of the files, but two files are stubborn and I can also not pause them in the interface. now it keeps trying to download these two files over and over again?

[r3klawz]

for the most part it worked very well and downloaded the bulk of the files, but two files are stubborn and I can also not pause them in the interface. now it keeps trying to download these two files over and over again?

I'm seeing the same. Removed files seem to get stuck in limbo. Once manually removed, downloads resume. But I am seeing other files that are not removed also getting stuck until "paused", at which point they flip to completed.

[jarvis2f]

I noticed that the file seems to have already been deleted on the Telegram client side, so I suspect this is the reason why the file status was not updated correctly.

I tried the following steps to reproduce the issue:

1. Account A sends a 200 MB file in a channel.
2. Then account B starts downloading it via telegram-files, while account A deletes the file.
3. I then observed that the file status on telegram-files changed to idle and the download was paused.
4. After refreshing the page, the corresponding record disappeared.

At this point, I’m not sure how I can reliably reproduce this issue in order to help you troubleshoot and fix it.

[TimetravelerDD]

I checked and all the files are actually still available in in telegram (7 files with the same name). i think the issue in my case is a renaming conflict.

notice how most files with an identical name got renamed. but the one that is a candidate for reconciliation does not and maybe fails because of this? ist's just strage that it says "missing original message".

perhaps the reconciliation algorithm needs the name conflict detection implemented as well? (sorry I don't understand the code if it's already there)