I haven’t been able to test this yet, but I think this may have to do with the order that odrive is seeing the operations. All moves are optimizations of a delete + add. odrive can only detect operations based on object states, so it has to interpret the intent for a move.
If you were to wait long enough, odrive will initiate its own routine local scan and pick up both the add and the delete for the placeholder file and be able to optimize that move. When you want it to be done immediately, you can issue the refresh on the folder where the file was moved from (odrive sees the file has been deleted), then a refresh on where the file was moved to (odrive will see the new placeholder and correlate it to the previous delete)
The CLI doesn’t have an individual restore command, but you can simulate a single restore by creating placeholder file where the file was deleted. For example, if you deleted
/test/test.txt you can restore it with
touch /test/test.txt.cloud. If it was a folder you would use
.cloudf instead of
Are you a premium user, or are you using the free version of odrive?