Folders being detected as files, glitch

[raccoon]

Strange bug or glitch I noticed just now. It seems that a large chunk of the indexed folders are being identified as files instead of folders.
It should be noted that just about every folder name contains periods '.' in them. Notice the size and timestamps disappear, and the file extension, type and attributes change. I wouldn't know what to make of this glitch, but a rescan of the disk squared it away. I don't recall having noticed this behavior before.

The drive is an exFAT format.

https://i.imgur.com/kufCKKb.png

[void]

If Everything is unable to determine the attribute of a filename, it will default to file over folder.

It is possible that Everything indexed the filename, but not the file's attributes due to the disk being offline.

The next scheduled rescan should correct the issue or you can force a manual rescan as you have done.

[raccoon]

Hi void,

You have it backwards though. Those are all folders. Everything started incorrectly identifying them as files instead of folders. I believe this happened after moving the collection of folders and their contents from the root path to a sub folder. Somehow Everything saw the folders as files after the move. So perhaps the monitoring function for exFAT is not quite right.

[NotNull]

You have it backwards though. Those are all folders. Everything started incorrectly identifying them as files instead of folders.

That is exactly what @void is saying :

If Everything is unable to determine the attribute of a filename, it will default to file over folder.

[raccoon]

I see. So you're saying that because the attribute response never makes it, it never gets the "D" attribute and remains a "file" without any shape or form besides its name. Doesn't try again?

[NotNull]

Doesn't try again?

The next scheduled rescan should correct the issue or you can force a manual rescan as you have done.

[raccoon]

I guess I should rephrase. Does Everything know that an error has occurred during indexing, and attempt to retry the request or resolve the error? Is there any reporting so I can detect index errors before performing a routine of tedious nature, so I do not miss any work and have to undo everything and dig back in time?

[therube]

Perhaps something like this

type:folder !attrib:d !type:"compressed (zipped) folder"

might point out oddities?
(I don't have anything to test against.)

[NotNull]

file: !size:>=0

or

file: !dm:>=0-0-0

? (can't test it)

Or format the volume as NTFS. Then Everything will automatically pick up the missed changes the next time you connect it.