Hi @yukihyou,
Strange. I’m sorry to hear you ran into that issue with the “sync to odrive” relationship being lost. The new build only changed the way webdav integration functions, so it shouldn’t have removed any relationships. The relationship is stored in a local database in the .odrive folder in the user profile directory. The only thing that should affect that is an uninstall or some sort of external modification to the files in that folder, so I’m not sure what happened there.
“Sync to odrive” will not follow any local folder renames or moves. I have seen cases where a user renamed or moved the local folder in the “sync to odrive” relationship. When that happens the relationship is lost and the newly renamed/moved folder is no longer “seen” by odrive. If this does happen, however, the “old” folder should still be listed in the odrive menu under “sync to odrive”.
When using “sync to odrive”, you will need to keep in mind that the local system will be considered the “newest” source if there are file differences between the cloud and the local system when the relationship is created, even if the dates on the files are older. So, if sync to odrive was enabled (or re-enabled) on a local folder and the files differed from what it on the remote, odrive will assume that the user’s intent was to upload the local files to the remote storage. We’ve talked about creating more customization where you can specify which side should be the authoritative source in cases like these, where there are files differences, which would’ve been helpful for your use case.
I took a look at the diagnostic, but I don’t see anything abnormal. I suppose this is expected though, since it is working properly ;). I’m still not sure what was causing the lack of refreshing in the previous case.