Yes! FullStory records uncaught exceptions so you can identify sessions where errors are impacting your digital experience using Dev Tools, Search, Metrics and Dashboards. This helps you understand how many users were impacted and how urgent it is to prioritize a fix.
In order to search for uncaught exceptions, Console Recording must be enabled. Console Recording is enabled by default, however, if it has been disabled, you will not be able to search for uncaught exceptions until it is enabled again.
To identify uncaught exceptions, create a search using the "Uncaught exceptions" event filter.
To get more specific, refine your search using the "Web source file URL" dependent criteria for web or the "Mobile Source file" criteria for mobile.
Your search results will return a list of sessions impacted by uncaught exceptions. Watch a session and use Dev Tools to find and debug errors.
You can also track the impact of uncaught exceptions using metrics and dashboards. For example, these dimensionality cards show top uncaught exceptions by text and source file URL. 
Need a refresher on how to build metrics and dashboards? Check out our enablement course at learn.fullstory.com!
FAQs
Can I search for uncaught exceptions on both web and mobile?
You can search for uncaught exceptions on web and Android mobile apps. Searching for uncaught exceptions on iOS mobile apps is not available at this time.
Do I need to enable searching for uncaught exceptions in my FullStory account?
No. The ability to search for uncaught exceptions was released in March 2021. You'll be able to search for uncaught exceptions automatically for all sessions recorded after the release.
Can I search for any uncaught exceptions instead of a specific text string?
It's not possible to search for any uncaught exceptions, but you may be able to broaden your search results using substrings that contain common error type prefixes like TypeError, ReferenceError, and Uncaught.