OneDrive Storage failed to load

I saw these posts but the solution was always to reload the token. This cant be the case because i had to do it twice now. How do i fix this issue permanetly or what is the root cause of this problem? I need to rely on that piece of software…

Running backup command from /cache/localhost/0 to back up /data/user/Paperless_Export
Options: [-log backup -storage Paperless -threads 4 -stats]
2025-09-19 08:54:40.198 INFO REPOSITORY_SET Repository set to /data/user/Paperless_Export
2025-09-19 08:54:40.198 INFO STORAGE_SET Storage set to one://Server_Backups/Paperless
2025-09-19 08:54:40.198 ERROR STORAGE_CREATE Failed to load the OneDrive storage at one://Server_Backups/Paperless: invalid character '9' after top-level value
Failed to load the OneDrive storage at one://Server_Backups/Paperless: invalid character '9' after top-level value

I think that @saspus gave you both answers in that second thread:

Cause of problem:

Duplicacy instead of saving the token file contents, saves and encrypts(!) path to the token file. Which breaks most people workflow, who download to ~/Downloads folder, feed it to Duplicacy, and nuke that file, rightfully expecting Duplicacy to have ingested its contents.

Fix for problem:

The workaround would be to manually move the token to ~/.duplicacy_web or other persistent config directory and only then provide it to duplicacy.

Not that it helps you much, but I can also add: I found trying to use OneDrive Business a total nightmare, especially the throttling. In the end I quite trying to use it.

Thanks for your reply. First i use OneDrive Personal not business. Second, the token file can be regenerated and put in the same place as it was, then it works again, but i cant be doing this every month or so… I got the tokenfile stored on a secondary share which is mounted to the duplicacy container. i never touched the tokenfile. So i really dont know what the problem is with that…

I cant be the only person getting this error.

Do you have 2 jobs running at the same time? If so, there is a possibility that 2 jobs may attempt to update the same token file simultaneously which corrupts the file.

If the problem occurs again, can you share the token file with me (via PM) and I’ll take a look at it?

Oh actually i do have a job that runs in parallel. Never thought of that to be honest. Thanks for pointing out! I will change that and see how it goes. Might do the trick!