Inconsistent behavior between Verify Location and Retrieve Location when a device is roaming.

In situations when the device is roaming it might not be possible to get its location. When this happens we have different behaviors.

Verify Location - It looks like two possible responses (and it is not obvious from the documentation which one will be responded)

• 200 with verification result UNKNOWN
• 422 LOCATION_VERIFICATION.UNABLE_TO_FULFILL_MAX_AGE "Unable to provide expected freshness for location"

Retrieve Location - It looks like two possible responses (and it is not obvious from the documentation which one will be responded)

• 404 LOCATION_RETRIEVAL.DEVICE_NOT_FOUND "The location server is not able to locate the mobile"
• 422 LOCATION_VERIFICATION.UNABLE_TO_FULFILL_MAX_AGE "Unable to provide expected freshness for location"

First thing to do is to document the expected behavior per API, that is when will you receive a 200/422 and 404/422.

Optionally we might want to revisit if we want to keep 200/422 for Verify Location or if we want to align with Retrieve Location and use 404/422 instead.