You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Queued local files keep stale paths after a vault move #412
Queued local episodes keep stale file paths after a vault file moves. When playback auto-advances to that entry, PodNotes reports that it cannot load the media even though the file still exists at its new path.
Observed in Obsidian 1.13.7 on Linux while verifying moved-file timestamp links. Fixtures/Clip+One.wav was queued through PodNotes, then moved to Fixtures/A/Clip+One.wav. After another local item ended, the queue advanced to the old entry. The player reported status: "error", the selected episode retained filePath: "Fixtures/Clip+One.wav", and the moved file remained in the vault. The direct timestamp-link fallback correctly found the moved file; queue playback does not use that resolver.
The OWNKEY runtime evidence records this state in rc-finding3-unregistered.log before its first URI action. This is outside the scoped fix to timestamp-link fallback, and no queue or rename tracking changes are included there. Investigate updating local snapshots on vault rename while preserving the existing ambiguous-file safety rule.
Activity
fix: follow vault moves for local files and play linked vault files o…