Old/Incorrect solar system ID returned from Character Location

[Slazanger]

Bug

The Character Location api is returning the incorrect system. It appears to be the system I was in at downtime

Request

GET /v1/characters/xxxxx/location?datasource=tranquility

Response

OK

Status Code

200

Headers

X-Esi-Request-Id: 73fb4945-fdb5-4a14-a655-b6a566d3717d
Date: Mon, 10 Sep 2018 16:25:00 GMT
Last-Modified: Mon, 10 Sep 2018 16:25:00 GMT

Body

{
	"solar_system_id":xxxxxxx,
	"structure_id":yyyyyy
}

Expected

This is returning the system I was in at downtime, I've since moved a few systems over and have docked in another structure; however this hasnt been updated

Checklist

Check all boxes that apply to this issue:

• Bug description is provided
• Request path is provided
• Response status code is provided
• Response headers are provided
• Response body is provided
• Expected response is provided

[ddavaham]

Can you please provide "snapshots". For example, make the request, then login and move a couple of jumps, and make the request again. This endpoint has an incredibly short cache timer and this may just be a fluke. I just tested this myself with a JF pilot and the endpoint updated the solar system id and station id immediately after the cache expired.

Include whatever details you feel comfortable providing, bare minimum being the request id as you did with this request.

[Slazanger]

This is occurring on 1 of the 3 characters I've tested; and has been occurring since just after down time today..

Another request :
X-Esi-Request-Id: 082e5baa-6a93-4d32-9088-d2b117e78492

[Slazanger]

And Jumped a System over again.. and its still not updated

X-Esi-Request-Id: dbcde203-0f85-4e9c-ac13-657db7caa2fc

[ddavaham]

Thanka Sir. This will be a perfect example for the Devs

[ddavaham]

Duplicate of #828