Prune -exhaustive -exclusive -keep 0:1 -a -storage XXX doesn't delete everything

Shouldn’t the above comand delete all snapshots? Instead there is still one snapshot left (not sure if it would delete other snapshots, there was only one to start with)

When was the one snapshot created? If it was created within the last 24 hours it may not get deleted.

Those snapshots (from multiple IDs) are from August.

Rerun with -d -v (duplicacy_win_x64_2.7.1.exe -v -d prune -storage my_storage -exhaustive -exclusive -threads 16 -a -keep 0:1) and the output is something like:

...
Chunk fff...96 is referenced
Chunk fff...48 is referenced
Listing snapshots/
Listing snapshots/aaa/
Listing snapshots/bbb/
Listing snapshots/ccc/
Listing snapshots/ddd/
Snapshot aaa revision 98 needs chunk ad...c9
Snapshot bbb 3 needs chunk bf...1a
Snapshot ccc 1 needs chunk 59...de
Listing chunks/
Listing chunks/fe/
Listing chunks/fd/
Listing chunks/fc/
Listing chunks/fb/
Listing chunks/fa/
Listing chunks/f9/
...
Listing chunks/01/

And then finishes.

I don’t know what that means. Each of the IDs only has one snapshot.

The CLI process may get killed due to out-of-memory. Check ~/.duplicacy-web/logs/duplicacy_web.log for any errors.

I was running this manually in the console. Can’t find any logs in duplicacy_web.log. Also from eye-balling the task manager the memory never goes over 60M. Is there a better way to debug this?