Basically the title. I haven’t really been able to pinpoint when it happens, seems random, so I assume it’s a race condition issue between file creation and file opening.
This one gets reported from time to time, so I’ll try to explain what’s usually going on.
1) “File X not found” happens every time
In most cases, the Destination’s Target Vault path needs a manual adjustment. Quick Draft does its best to detect which folder in the Destination path is the Vault root, but it can’t always determine this correctly.
2) “File X not found” happens only sometimes
The most likely cause is Obsidian’s internal indexing. The note is created externally, but Obsidian hasn’t finished indexing yet, so when it tries to resolve the URI, it shows “File X not found.” Unfortunately, Quick Draft can’t influence this—indexing is fully handled by Obsidian.
Quick test to confirm it’s indexing-related:
Force-close / dismiss Obsidian from the recent apps list
Create a new note with Quick Draft
Open Obsidian (any page is fine—just let it load so indexing can happen)
Force-close Obsidian again
Try opening the note from Quick Draft history
If the note is consistently found in this flow, it’s almost certainly an Obsidian indexing issue. If it still fails, please let me know.
P.S. From my experience, I haven’t been able to reproduce this on the latest Obsidian versions.
huju
•
Feb 8
Yeah, I did the test that you described (I assume you meant to test with a route that doesn't open Obsidian automatically right?) and the test does consistently find the note.
However, I also did an altered version of your test where I skip step 3 and 4 and that also works consistently. So to me that points more towards a race condition between file creation and Obsidian file indexing rather than file indexing alone. If that's correct, then a short delay between creating the file on the disk and triggering the URI resolution would probably fix the issue, right? What do you think, does that make sense?
Again, thanks for the great app, it's really useful! Would be happy to help test if you can't reproduce the issue locally.
Serhii Petrenko
Team•
Feb 8
App update is available for download. It includes both the the delay before opening a note and a fix for the template not being applied when saving a file without a note.
Please let me know if the issue persists, and include your device model and Obsidian version.
Comments4
Serhii Petrenko
Feb 8
This one gets reported from time to time, so I’ll try to explain what’s usually going on.
1) “File X not found” happens every time
In most cases, the Destination’s Target Vault path needs a manual adjustment. Quick Draft does its best to detect which folder in the Destination path is the Vault root, but it can’t always determine this correctly.
2) “File X not found” happens only sometimes
The most likely cause is Obsidian’s internal indexing. The note is created externally, but Obsidian hasn’t finished indexing yet, so when it tries to resolve the URI, it shows “File X not found.” Unfortunately, Quick Draft can’t influence this—indexing is fully handled by Obsidian.
Quick test to confirm it’s indexing-related:
Force-close / dismiss Obsidian from the recent apps list
Create a new note with Quick Draft
Open Obsidian (any page is fine—just let it load so indexing can happen)
Force-close Obsidian again
Try opening the note from Quick Draft history
If the note is consistently found in this flow, it’s almost certainly an Obsidian indexing issue. If it still fails, please let me know.
P.S. From my experience, I haven’t been able to reproduce this on the latest Obsidian versions.
huju
Feb 8
Yeah, I did the test that you described (I assume you meant to test with a route that doesn't open Obsidian automatically right?) and the test does consistently find the note.
However, I also did an altered version of your test where I skip step 3 and 4 and that also works consistently. So to me that points more towards a race condition between file creation and Obsidian file indexing rather than file indexing alone. If that's correct, then a short delay between creating the file on the disk and triggering the URI resolution would probably fix the issue, right? What do you think, does that make sense?
Again, thanks for the great app, it's really useful! Would be happy to help test if you can't reproduce the issue locally.
Serhii Petrenko
Feb 8
App update is available for download. It includes both the the delay before opening a note and a fix for the template not being applied when saving a file without a note.
Please let me know if the issue persists, and include your device model and Obsidian version.
huju
Feb 8
Both issues seem to be fixed, thanks a ton!!