Describe the Bug
The location filter is now way too overactive, previously it had a subtle effect on responses now it constrains responses that should use global data to only specific regional data.
This is a new change (last few days we have noticed it with no changes to our code)
Expected Behavior
When the user asks a query which benefits from location data such as “Where is the nearest restaurant” then of course use location data. But when the query is general, an example I have seen is “What end markets does ITT serve” then we should be using global context.
Actual Behavior
Responses try to use hyper specific region data when not needed. For example “What end markets does ITT serve” tries to figure out which services ITT provides for the specific coordinates of the user which returns a useless response.
Steps to Reproduce
- Call the API with the following request: user location filter with coordinates
- Observe the unexpected behavior.