Is HSSNotFound still the right response, or should we be creating a separate HSSOverloaded exception?

It may be that it's too much work to catch HSSOverloaded as well everywhere we catch HSSNotFound, though.