This appeared on 2 of the 11 receiving Windows devices.
The folder is created by a script that changes the config and usually the path is then created by Syncthing on the remote devices. I could not find any error messages why the path could not be created.
I checked for the path on the machines and it was not there.
I reran the parts of the script that share the folder and this time the folder was shared on all devices.
Do you have any idea what could have caused Syncthing to not create the folder the first time?
I could append the date to the folder ID, but the problem should not really exist since the folders are removed from the config through the API and restarted 1h before the sync process begins due to my problem with the slow down of the sync.
Yeah. But it sounds like you do run into several odd problems, and without being able to share clear logs you might not be able to get much help. I still suggest looking at resource usage (closely; including I/O latency & queues, etc) when you see issues and when you don’t. You may be triggering some corner case by the unusual config changes etc.
I know there was a bug where the folder id to int mappings were not dropped, and I know my fix dropped it on restart, because if lets say you shut down syncthing, modify the config externally, and start it back up, that would not clean up everything. Perhaps dropfolder drops the ids too, but I am on the phone, hence can’t check.