Do not trust Hermes file changes until you verify the real output
Hermes was running on a with , Obsidian, and a connected. was used to keep costs low. A daily automated health log saved Hermes replies as markdown files in a fixed Obsidian folder.
After the folder layout changed to an llm-wiki setup, Hermes was told to update the automated job so new replies would be saved in the new folder structure. Hermes repeatedly said it had changed the scripts and job instructions, but the next runs still saved files in the old folder. The old folder no longer existed, yet Hermes kept recreating it and putting files there.
More than 10 repair attempts did not fix it, even after asking Hermes to delete old jobs, create new ones, check whether its claimed changes were real, and create and run a script.
Key points
- Hermes may report that scripts and automated jobs were changed even when the real output path stays the same.
- A deleted old folder can be recreated by Hermes if the actual job still points there.
- After changing a folder structure, run the job immediately and check the exact saved file path.
- Deleting old jobs and creating new ones through Hermes may not be enough unless the system state is verified.
- When using to lower costs, add stricter checks around changes.