state is missing in reverse geocoding

The Florida relation was broken in early January. It has been fixed in the meantime but you still caught the bad version with your import, so the boundary for Florida is missing. Here is a way to update your database for such broken objects without a reimport:

1. Import the latest version of the object in question. You need to find the OSM type and id of the object, for example by searching on osm.org. Florida is here. For the import, the update script can be used, i.e

   ./utils/update.php --import-relation 162050 --index
   

2. Check that the import worked by searching for the object in your local instance. If it didn't work, the object might still be broken and you have to fix it in OSM first. Find out the place_id of the object by looking up details in your instance. For example, Florida on the osm.org instance is here, so the place_id is 97976186. The ids are different for every instance.

3. Update any places in your database that depend on the object, e.g. for Florida again:

    psql -d nominatim -c 'select place_force_update(97976186)'
    ./utils/update.php --index --index-instances 2
   

   Be warned that this may take a long time for an area as large as Florida.

If you run updates on your database, (1) will happen automatically. Dependent places, however, will not be updated for larger areas for performance reasons, so you may still want to do (2) and (3).