Failed to resurrect the chunk?

My overnight run of Duplicacy produced the following error. Not quite sure what to do about it, if anything needs to be done. First time it has happened. Any thoughts or suggestions would be most appreciated.

2019-04-09 03:02:30.591 ERROR FOSSIL_RESURRECT Failed to resurrect the chunk 2781de315d1f44c2ea5448402627e64e80c4c8696a5bc22f1822523743c6d0a3 from the fossil chunks/27/81de315d1f44c2ea5448402627e64e80c4c8696a5bc22f1822523743c6d0a3.fsl: 400 Must provide one of the following facets to create an item: Bundle, File, Folder, RemoteItem

The backup in question is set to be pruned, with snapshots deleted after 1825 days (which I’ve not yet reached since starting to use Duplicacy), keeping one snapshot every 30 days after 30 days, and one snapshot every 7 days after 7 days. Running v. 2.1.2 on Windows 10.

Which storage is this?

The error basically means it couldn’t rename chunks/27/81de315d1f44c2ea5448402627e64e80c4c8696a5bc22f1822523743c6d0a3.fsl to chunks/27/81de315d1f44c2ea5448402627e64e80c4c8696a5bc22f1822523743c6d0a3. To fix it, you can just rename it manually via the web interface provided by the storage provider.

Thanks for the quick reply. The storage is MS OneDrive.

Thank you also for the suggestion, but when I go to that directory on OneDrive, there is no such file there. There also doesn’t seem to be any .fsl files at all. Consequently, I’ve not been able to rename it. Do let me know if you have any other suggestions.

Run a check command to see if there are any unreferenced chunks (duplicacy check -a). If you want to dig deeper, the prune logs under .duplicacy/logs should tell you what happened with that particular chunk.