I have been syncing across Team Drives using --max-age for filtering files to be synced. During this, I noticed some files were being transferred which shouldn't fall within the max-age set.
To confirm whether this was an issue with the filtering or something on the drive itself, I checked via the WebUI and it seems to show a very wrong modification time of Jul 28, 2017, by <user> when the created at date is Jun 28, 2019.
This is almost a 2-year difference. Any thoughts on this could have happened?
Makes sense if it's just keeping the original file(s) modified timestamp, but doesn't it seem logically wrong to have a greater created at timestamp than the modified timestamp?
I mean, I can see either way but I believe the problem is the created date can't be set of GD as the only thing available is the modified date so that is what gets set and what the mount uses as well.