Unhelpful message from Dyalog editor when source file no longer exists

[aplteam]

This message makes no sense:

1. It tells me that the file has vanished and asks me whether I want to
   re-load the vanished file. That makes no sense.

2. The path of the file in question should show as part of the
   message, not the caption.

3. The path is wrong: C:\src does not exist.

4. The caption of the message box does not show the process ID, and not
   even that it comes from Dyalog

   I have {PID} {WSID} {PRODUCT} on Computer\HKEY_CURRENT_USER\SOFTWARE\Dyalog\Dyalog APL/W-64 19.0 Unicode\Captions\MessageBox.

   When the dialog box showed, I had 6 APL sessions open, three of which were running code; in the others, I was tracing/editing stuff.

5. Shouldn't the list of actions it suggests to take be an ordered list?

I have no idea how I got into this. Yes, I looked at Conga's LIB, but I did not change anything, not even by accident: I have "Confirm edit window close on Fix" always on.

]link.status
 Namespace       Source                                                                    Files 
 ⎕SE.Link    ←→  C:/Program Files/Dyalog/Dyalog APL-64 19.0 Unicode/StartupSession/Link       34 
 ⎕SE.Dyalog  ←→  C:/Program Files/Dyalog/Dyalog APL-64 19.0 Unicode/StartupSession/Dyalog      4 
 #.Tatin     →   C:/T/Projects/Dyalog/Tatin/APLSource                                       1481 

Dyalog  19.0.48436 64-bit Unicode, BuildID 246567e8            
 OS      Windows 10 or Windows Server 2016 (10.0.19045) 64-bit  
 Link    4.0.12                                                 
 SALT    2.915                                                  
 UCMD    2.6                                                    
 .NET    .NET Framework 4.8.9181.0                              
 WS      19.0                                                   

[mbaas2]

That problem has nothing to do with Link. It was caused by a problem with DBuild's nosource modifier.

[mkromberg]

The Conga workspace was saved with links to a folder on a build machine at Dyalog. There are two issues here, the one in DBuild which has been fixed, and a badly worded error message from the interpreter.