Alaska AER office 500 error on /offices/AER query

[ktrue]

Queries to https://api.weather.gov/offices/AER result in

{
    "correlationId": "36cf3bf8-1c14-454f-99f5-ad4b7652e903",
    "title": "Unexpected Problem",
    "type": "https://api.weather.gov/problems/UnexpectedProblem",
    "status": 500,
    "detail": "An unexpected problem has occurred.",
    "instance": "https://api.weather.gov/requests/36cf3bf8-1c14-454f-99f5-ad4b7652e903"
}

here's the details/headers for the fetch. It seems to be a persistent issue (multiple days now)

<!-- curl fetching 'https://api.weather.gov/offices/AER' -->
<!-- HTTP stats:  RC=500 dest=104.119.184.17 port=443 (from sce=74.208.252.86)
      Times: dns=0.061 conn=0.075 pxfer=0.110 get=0.185 total=0.295 secs -->
<!-- headers returned:
HTTP/1.1 500 Internal Server Error
Server: nginx/1.16.1
Content-Type: application/problem+json
Access-Control-Allow-Origin: *
Access-Control-Allow-Headers: Feature-Flags
X-Request-ID: 552c60db-5f69-41f5-9103-a657baba968e
X-Correlation-ID: 552c60db-5f69-41f5-9103-a657baba968e
X-Server-ID: vm-bldr-nids-apiapp12.ncep.noaa.gov
Pragma: no-cache
Content-Length: 325
X-Akamai-Request-ID: c056b09.2ce3aff
Cache-Control: private, must-revalidate, max-age=86400
Expires: Fri, 26 Jun 2020 16:44:41 GMT
Date: Thu, 25 Jun 2020 16:44:41 GMT
X-Cache: TCP_MISS from a104-119-189-182.deploy.akamaitechnologies.com (AkamaiGHost/10.0.5-29826511) (-)
Connection: keep-alive
Vary: Accept,Feature-Flags,Accept-Language
Strict-Transport-Security: max-age=31536000 ; includeSubDomains ; preload
 -->

[ktrue]

It's been 15 days, and still it's happening:

<!-- curl fetching 'https://api.weather.gov/offices/AER' -->
<!-- HTTP stats:  RC=500 dest=23.1.244.20 port=443 (from sce=192.168.1.104)
      Times: dns=0.001 conn=0.016 pxfer=0.048 get=0.420 total=0.467 secs -->
<!-- headers returned:
HTTP/2 500 
server: nginx/1.16.1
content-type: application/problem+json
access-control-allow-origin: *
access-control-allow-headers: Feature-Flags
x-request-id: af169d8e-4751-4b32-82b5-cde2f6cc477c
x-correlation-id: af169d8e-4751-4b32-82b5-cde2f6cc477c
x-server-id: vm-bldr-nids-apiapp8.ncep.noaa.gov
pragma: no-cache
content-length: 325
x-akamai-request-id: 165cb36c.80f6fd0
cache-control: private, must-revalidate, max-age=86352
expires: Sat, 11 Jul 2020 18:53:32 GMT
date: Fri, 10 Jul 2020 18:54:20 GMT
x-cache: TCP_MISS from a104-123-69-196.deploy.akamaitechnologies.com (AkamaiGHost/10.1.0-29986438) (-)
vary: Accept,Feature-Flags,Accept-Language
strict-transport-security: max-age=31536000 ; includeSubDomains ; preload
 -->

[StephenClouse]

Well, it shouldn't throw a 500, but I wouldn't expect this to work regardless, since AER is not an office.

It's part of the Anchorage office (AFC). Their coverage area is split into two domains (AER and ALU) due to technical reasons.

If you're seeing a link to AER or ALU in something other than /gridpoints, that would be the actual bug.

[ktrue]

If I do a 'https://api.weather.gov/points/61.2181%2C-149.9003', it returns

"properties": {
    "@id": "https://api.weather.gov/points/61.2181,-149.9002999",
    "@type": "wx:Point",
    "cwa": "AER",
    "forecastOffice": "https://api.weather.gov/offices/AER",
    "gridId": null,
    "gridX": null,
    "gridY": null,
    "forecast": null,
    "forecastHourly": null,
    "forecastGridData": null,
    "observationStations": null,

the gridpoint data is missing .. shouldn't it be there?

If I do a query closer to home 'https://api.weather.gov/points/37.2747%2C-122.0229' it returns

    "@id": "https://api.weather.gov/points/37.2747,-122.0229",
    "@type": "wx:Point",
    "cwa": "MTR",
    "forecastOffice": "https://api.weather.gov/offices/MTR",
    "gridId": "MTR",
    "gridX": 97,
    "gridY": 101,
    "forecast": "https://api.weather.gov/gridpoints/MTR/97,101/forecast",
    "forecastHourly": "https://api.weather.gov/gridpoints/MTR/97,101/forecast/hourly",
    "forecastGridData": "https://api.weather.gov/gridpoints/MTR/97,101",
    "observationStations": "https://api.weather.gov/gridpoints/MTR/97,101/stations",

which allows a gridpoint forecast query correctly.

[StephenClouse]

Anchorage has this unique issue because of this technical split. It worked at one point but we broke it fixing a separate bug involving points on the Great Lakes (which have a similar issue where the forecast and warning responsibilities are split between two different offices).

We're still figuring out the right way to make everything work at the same time.