This database can be imported to tell Leverage to report information on failures that throw exceptions.  The most common example is user code that doesn't run successfully, so this can be a useful debugging tool.  It can be helpful if you are attempting to import data that Leverage is having difficulties with or if you are experiencing trouble with your card or internal store.

There are several places where Leverage traps exceptions and checks to see whether this database exists.  If it does then Leverage adds a human readable copy of the current exception to this database.  The database is indexed on the time the exceptions occur, so you would normally find the exception of interest toward the end of the database.  (Remember you can quickly get to the last record by tapping the up arrow from the first record in single record view.)