ID 599431 - Localized Clips in Nuke Studio/Hiero do not default to their original file path if the localized file cannot be found

Problem summary:
Localized Clips in Nuke Studio/Hiero do not default to their original file path if the localized file cannot be found
 
Customer reported version:
Hiero N/A
 
Customer reported platform:
Alma 9
 
Steps to reproduce:
1) Launch Nuke Studio and navigate to File > Import File(s)...
2) Select some media, and double-click the imported Clip in the Project Bin
3) Once the Properties panel opens, change the Clip's Localization Policy to "on demand"
4) Press the updateLocalization button
5) Open a file browser and navigate to the localization directory
6) Delete the localized files from disk
7) In Nuke Studio, close and reopen the Clip Viewer
8) Observe the DDImage::OpenedFile:open failed: {path to localized file}: Read error: No such file or directory that now appears in the Viewer and Terminal:

 
Expected behavior:
If a Clip's localized media no longer exists, Nuke Studio/Hiero should default to using the original media.
 
Actual behavior:
When localized media is removed or otherwise cannot be located by Nuke Studio/Hiero, a "No such file or directory" error will appear.
 
It is not possible to resolve the issue by setting the Clip's Localization Policy to "off" (or any other value), refreshing or reconnecting the Clip (via Python or the UI), or forcing validation of the Clip's Read node. Nuke Studio must be restarted or the media needs to be re-localized to remove the error message.  
 
Workaround:
Besides restarting the application or executing the Clip's updateLocalization knob, there is no known workaround at this time.
 
Reproduced by Support in:
Nuke Studio 16.0v2 - Windows 11, macOS 14 Sonoma
Nuke Studio 15.0v1 - Windows 11
Nuke Studio 14.0v1 - Windows 11
Nuke Studio 13.0v1 - Windows 11
Nuke Studio 12.0v1 - Windows 11
 
Earliest version tested:
Nuke Studio 12.0v1 - This issue appears to be in all tested versions of the product