Error Log

[MrDaisyBates]

Bug Report

Message for user

File not found in vault.

Error Message

File not found at path: Supporting Notes/Templates/New Note.md

Context

MarkdownFileOperations.ts/readDataOfVaultFile

System Information

Obsidian version: 1.11.7
Installer version: 1.8.10
Operating system: #1 SMP PREEMPT_DYNAMIC Fri Jan 30 20:23:28 UTC 2026 6.18.8-200.fc43.x86_64
Use [[Wikilinks]]: true
Base color scheme: dark
Community theme: none
Snippets enabled: 0
Plugins installed: 8
Plugins enabled: Vault Statistics v0.1.3
Task Board v1.9.1
Reminder v1.1.21
Spaced Repetition v1.13.4
Advanced Canvas v5.6.6

Any additional information and screenshots

Not really sure why this is popping up, but it asked me to share it with you, so I am.

"Supporting Notes" is a subfolder in my vault. "Templates" is a subfolder under it. Supporting Notes has been there for ages. Templates is a new folder.

"New Note.md" is just a new markdown file I made in Tangent via...well, you have Tangent. I'll just tell you.

• Folder in the sidebar on the left
• CTRL+Click to open it
• Inside the folder, click the button to create a new note

It would have been titled New Note.md when created, but I named it something else (because "New Note" is a placeholder, obviously).

So, idk if the renaming behavior or something triggered this bug on your end. Obsidian was open for all of this and in the background.

I have seen these errors from Task Board before. They seemed benign, so I ignored them. I'm sure you'd prefer to resolve the behavior, though.

If you have any questions for me, feel free to ask. I gave you most of what I know, I believe. I'll let you know if I isolate anything more specifically than that.

[tu2-atmanand]

So, idk if the renaming behavior or something triggered this bug on your end. Obsidian was open for all of this and in the background.

You are absolutely correct here. And this is definitely related to #653 .

Thank you for sharing the details which lead to this bug. This is something the Bug reporter cannot capture and hence I have kept the "Any additional information and screenshots" section to get these kinds of more information. Helps to understand the root cause of the issue much faster.

Will work on this soon. Should be easy to fix this...

[tu2-atmanand]

I believe here two bug reports must have shown. This was also not a good idea, so moving forward only one bug report will be shown and rest of the related bugs reports will be added into the log file.

If its possible can you please export the log file and share it to me on email (sanketgauns8@gmail.com) or here. Please check the log file content if there is any vault content which has been captured inside the logs before sharing it.

Logs can be exported using a button in settings under general tab.

[tu2-atmanand]

I have applied a possible fix to this issue. Let me release v1.9.2 and lets see if that fixes this issue.

Moving for review.

[MrDaisyBates]

Yeehaw! Thanks for the attention to this matter.

I have looked under Obsidian's "General" tab as well as Task Board's and I do not happen to see any option to export a log. I made sure to look a compulsive number of times. Let me know if I'm doing something wrong or if it's actually somewhere else.

[MrDaisyBates]

I see you are or just pushed an update. My Obsidian is currently failing to update the plugin. I'm guessing maybe it needs a few more minutes or something.

[tu2-atmanand]

So sorry for that. I realized, there was a bug introduced in the version 1.9.1, because of which everything under the "General" tab settings were hiding. Fixed that now.

I have just released the new version. You may try again now, it should update, its Obsidian internal mechanism which doesnt allow any plugin to install, until its release notes are published.

Hopefully, this specific bug should be fixed in this new version. I have replicated this exact steps with Tangent, and looks like this issue has been fixed. But, let me know if any other related issue happens.

[MrDaisyBates]

task-board-logs.txt

Here you go. Nothing too sensitive that I notice at first glance, so, I'm fine to share it here.

I do want to point out that it states I'm using 1.11.5, but I'm using 1.11.7

I'm not sure if that's just a simple logging bug or of that version detection issue is actually rooted in the entire plugin and could cause issues across versioning or something.

Thanks for the update!

[tu2-atmanand]

Here you go. Nothing too sensitive that I notice at first glance, so, I'm fine to share it here.

Yeah, there was no related log found. But, I hope this issue has been fixed in the last latest version 1.9.2.