This was encountered when I attempted to update the EF AISBL logo when testing another issue. We should probably look at handling this more gracefully when failing.