Skip to content
Discussion options

You must be logged in to vote

@darrepac
What should be happening is that when a file is modified locally / time is manually changed, the updated timestamp should trigger the client to use the API to update the timestamp on the remote file.

This possible could be a bug, but also might not be a bug because the OneDrive (online / remote) based on timestamp thinks it is 'newer', thus, will not update the timestamp of the remote to prevent sync issues / data-loss etc in-case the client is wrong about what the true state of the timestamp is.

Replies: 1 comment 5 replies

Comment options

You must be logged in to vote
5 replies
@darrepac
Comment options

@abraunegg
Comment options

@darrepac
Comment options

@darrepac
Comment options

@abraunegg
Comment options

Answer selected by abraunegg
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants