If you use )CLEAR or )LOAD following a Link which created a file system watcher, and you are using .NET 6.0 or later, this leaves the FSW's in "limbo". Changes to files in the previously linked folder (and possibly other changes) can cause APL to crash, sometimes disappearing without a trace. There may be other ways to end up in this situation, but the above is reproducible.
If you use )CLEAR or )LOAD following a Link which created a file system watcher, and you are using .NET 6.0 or later, this leaves the FSW's in "limbo". Changes to files in the previously linked folder (and possibly other changes) can cause APL to crash, sometimes disappearing without a trace. There may be other ways to end up in this situation, but the above is reproducible.
(APL crashes)
Resolution will require interpreter changes - there is nothing Link code can do to protect itself, but is logged as a Link issue as well.