ESI reporting incorrect character location

[Slazanger]

Bug

Character Location doesn't update after either a jump clone or a podding

Request

/v1/characters/ [ id ] /location

Response

The return is the system you cloned from or died in and not the system you respawn in. It stays this way until you gate/bridge to another system

Expected

After pod jumping or re-spawning in a medical clone the characters location to be correct

[Slazanger]

Just a little more detail : this will continue to report the wrong system until you un-dock into space

[Seavert]

Sounds great from #313 perspective.

[ddavaham]

Just closed several duplicate issues all related to this one. Please use this issue has the root for Frozen Location issues with the /characters/{character_id}/locations endpoint.

[Zoibderg]

Encountered this issue a few days ago. None of the above has fixed the issue. When the cluster shutdown happened last night my location was updated to the system that I was in during the shutdown, but it’s now stuck on that location.

Ah, interesting!

/me wanders off to test

Location does not update after pod death: Confirmed
Location does not update after jump clone from station to station: Could not reproduce

I'm going to do some testing to see if there's a difference between JC'ing between stations and citadels, but if anyone has extra info along these lines it'd be really helpful.

[chigaze]

I have had this occur when I have not been podded and have not clone jumped. Also it has persisted through downtime (although location was moved to location at downtime it remained stuck at the location). It is happened sporadically over the last year and half.

I do not know if this is the same issue, a related issue, or something else entirely.

[chigaze]

Both characters on my account are not tracking today. No clone jumps or podding.

Not sure if this is a commonality or not but I spend a lot of time in wormholes and flip back and forth between characters on this account.

[curs0n]

Experienced this very bug just today. Started after Downtime on the 14th of Nov, and still ongoing as of now. Hoping for downtime today (15th) to clear it.
It was not triggered by podding, or any Abyssal activity. Just plain normal jump cloning.