# No Status or Details by Completing previous backup **URL:** \ **Category:** Support\ **Created:** [May 10, 2026, 3:19pm UTC](https://forum.duplicati.com/t/no-status-or-details-by-completing-previous-backup/22384 "2026-05-10T15:19:27Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![ts678](https://forum.duplicati.com/letter_avatar_proxy/v4/letter/t/8491ac/32.png) [@ts678](https://forum.duplicati.com/u/ts678)\ **Post date:** [May 10, 2026, 9:25pm UTC](https://forum.duplicati.com/t/no-status-or-details-by-completing-previous-backup/22384/2 "2026-05-10T21:25:17Z")
Is this Docker? GUI says “No version yet”, but was there a prior attempt at one? If you did one, interrupted it, and are trying again, it will try to record what it had managed to get on the interrupted backup attempt, plus prior backup if it’s there. This case is described [here](https://forum.duplicati.com/t/errors-with-ftp/19576/5), with a deep description [here](https://forum.duplicati.com/t/stopnow-backup-and-cancellation-tokens/16223/24) and current work [here](https://forum.duplicati.com/t/completing-previous-backup-following-update-to-latest-2-3-0-1/22345), showing analysis of its slowness, a `disable-synthetic-filelist` workaround, and a speedup for any willing testers of [Release: 2.3.0.102 (Canary) 2026-05-09](https://forum.duplicati.com/t/release-2-3-0-102-canary-2026-05-09/22383). > ## Synthetic Filelist Optimization > > Optimized the creation of synthetic filelists, improving performance for large datasets. If this sounds like your case and you don’t want to try to wait it out, you can try stopping backup (which might not work), or harder stop of service or container. EDIT 1: If you have any performance tools, the symptom of being stuck in slow SQL is sometimes one CPU core being fully used, however disk use might limit usage. If your system seems idle, then something else is going on and will need study. --- _[View the full topic](https://forum.duplicati.com/t/no-status-or-details-by-completing-previous-backup/22384)._