If a dynamic expression in your app references an option set that no longer exists, the Issue Checker won't flag it as a problem. The expression will show up in the editor (typically as "Get an option" with the original option set reference), but your app can still deploy without any warning. This can happen if you copied an expression from another app that had a different option set, or if the option set was deleted during app optimization.
What you might notice
A dynamic expression shows "Get an option" referencing an option set that doesn't exist in your app
No issue appears in the Issue Checker for the broken reference
The behavior may appear after copying elements from another app, or after deleting an option set
Workaround
There's no automated way to surface these broken references right now. The best approach is to manually review any dynamic expressions that use option sets — particularly in areas of your app where elements were copied from another project or where option sets were recently removed. Look for any expression showing an unrecognized option set name and update it to reference a valid one.
Status
We're aware of this gap and plan to address it as part of broader Issue Checker reliability and performance improvements. Adding new issue detections carries a risk of impacting editor performance and could prevent apps that currently deploy from continuing to do so, so we're treating it carefully as part of a larger set of improvements rather than a standalone fix.