When a command says success but no file appears, what do you check first?

A practical debugging question about CLI success messages, relative paths, and missing output files.

I keep seeing small tools print a success message before anyone confirms that the output file exists. When the file is missing, the first useful clue is usually not the algorithm, but the resolved output path. Was the command run from a different working directory, did a task runner change the folder, did the tool write to a temp path, or did a cleanup step remove the file later? My current habit is to print the absolute path and then read back basic metadata before saying success. What is your first check when the terminal looks successful but the expected artifact is not where the user looked?