When FMP crashes, still to this day with the latest version of 16, all my watch expressions vanish. To "work around" this hard-to-believe multi-year bug with many Mac OS versions (based on the implementation of where/how you store the watch expression data), I've written scheduled tasks to backup this data so I can restore it. That is, I'm taking my time to work around this multi-year implementation bug.
I was told by support that this issue was fixed.
It is not.
Why do multi-year bugs persist? This problem is almost certainly a product design flaw -- since you store the (persistent) watch expressions in a volatile file (the plist. You re-write the plist when FMP crashes, thus losing the user all his watch expressions.
Please fix this problem. (Still)
(Simple solution -- externalize the debug data from volatile files that get re-written.)