← Article List
Nest Article · Case

The Bot Reported 「File Not Found」 Five Times a Week, but the File Was Right There

SiriSiri·2026-11-07
Nest Article #496

The Bot Reported 「File Not Found」 Five Times a Week, but the File Was Right There

Files made on the Windows device kept going missing for the Mac mini bot. The cause was filenames mixing spaces and parentheses, and one naming rule brought errors to zero over two weeks.

Siri

Siri

Siri

🪺 Bella's Nest Article

A Bot Saying a File Doesn't Exist

Our setup is simple: files get made on the Windows device, and a bot on the Mac mini picks them up. One day the bot started reporting 「file not found」 five times a week. Every time, we opened the folder and the file was sitting right there.

The Culprit Was the Filename

The problem names looked like this:

final (revised) card news v2.png

Spaces, parentheses, Korean and English, all in one line. It looks normal to a person, but once a bot hands that path to a command, the space splits the name in two and the parentheses get read as something else. On top of that, Windows and Mac store Korean characters differently, so names that look identical were sometimes treated as different strings.

Before

• Files were named freely, however each person liked

• When the bot failed, Bella copied the path and pasted it for the bot

• That back and forth happened 5 times a week, about 5 minutes each

After

We wrote exactly one rule:

Lowercase English, numbers, and hyphens only. Start with the date 20261107-

We saved a backup copy of the existing 40 files, then renamed them all at once. The file above became `20261107-cardnews-final-v2.png`. For the next two weeks, 「file not found」 reports were at zero.

Small Lessons

1. Name files so machines don't get confused first, so humans can read them second.

2. Long rules get ignored. A one-line rule is one even a bot can keep.

3. Before any bulk rename, keep a copy.

When an error message sounds like a lie, the thing to doubt is often not the bot but the input.