I am creating an automatic action that moves files to a directory after the creation date (year) and moved the file from December 30, 2025 to the 2026 folder
Why?
Hi @matboro1, thanks for joining the Community!
Are you referring to using the Dropbox automation feature?
Could you attack a screenshot showing the settings you've enabled for the automation?
This will help me to assist further!
Hi @Jay
Yes, i use it Dropbox automation feature (transfer files grouped per year)
Folder structure
Thanks, it's likely that the automation is moving files into the folders according to the date they were added to that specific folder, and not by the creation date of the file itself.
Could you confirm if you moved that file into the folder in 2026 and not in 2025?
I'm sorry I'm replying so late
I added the file to the 'bity-gotowce' folder on December 30, 2025 and the machine itself determined this file as having been created in 2026 (as can be seen in screenshot 1) and assigned it to the folder (which it created) 2026 - although in my opinion it should have added it to 2025
uncensored screenshot 1
Are there logs from this automation available anywhere?
While there aren't any logs for the automation itself, you can check the version history of the file to see the changes to that file, including its current location in your Dropbox account.
Does this occur for any other files created or modified in 2025?
no, this file is the only one with this error - I suspect it may be related to the end of the year (only then it turns out that the dropbox server clock is shifted)
I see 2 entries in the version history: addition (from the PC level) and modification (from the browser level - it is probably an automatic transfer to a given folder) - I compared it with another file from December 20, 2025, which "moved" well and has similar entries
Thanks for the additional details, @matboro1! It’s possible that this could be related to the server, but it’s hard to tell for sure, since this has affected only one of your files.
If you encounter the same issue in the future though, I'd like you to let us know here and we’ll be more than happy to investigate this further.
