Another instance of a contact (2 ops) on a Trail, and even though I specifically put in Kansas before I logged them, the log failed to show the state. It did update the distance after I refreshed the page.
Another instance this morning.
April log 04/26/26.
KC3YGJ - I manually entered Pennsylvania into the state / region before I logged it but the state failed to show up after being logged.
There have been a couple times things didn’t look correct in my log. After sitting for a couple minutes, Shift + refresh sorted things out, assuming we are talking about the web browser. When it comes to the browser, I seem to forget the obvious refresh when thing don’t look correct.
I have not started using the app yet.. one step at a time… LOL
Happy Logging
I had a couple more instances today and what I noticed was that even though I entered the state, when the contact actually hit the log the state was being removed. I think I reported the same thing a month or two ago.
If I went back in and edited the contact after it was logged, putting the state back in, the state then remained as part of the contact info and would be reflected in the log listing.
@W7YBY Hey Brian,
This is something that we’ve fixed in the past and i’ve got the team looking into how it got reverted. We’ll be pushing a fix for this soon as well as the distance issue.
Thanks & 73
Brad K4AZE
1 Like
@W7YBY Hey Brian,
So after digging into this some more i’m not able to replicate the state not being set when entering the park on my account or your account for some reason. After first, it does not add the distance like you mentioned but either after a refresh or waiting a few seconds it does pull in the distance properly.
I’ve got the team still looking into this though.
Thanks & 73
Brad K4AZE
I have see something like this if the POTA information comes in as AL,US.
The state does not get picked up when copy to log is used. I have to watch and select the state from the drop down. Frustrating especially on the mobile app.
Just wanted to mention my experience and see if it helps.
Rodney
AE5TX
Try it with another random park that’s a Trail, not an actual park.
1 Like
@W7YBY Yeah i just tried it with a couple of different “trail” parks.
It seems to be working as expected for myself and the team. To be clear I DONT think you’re crazy 
i think this has happened to you, we’re just not able to replicate it currently. Maybe with some of the other updates we’ve pushed yesterday and this weekend somehow it fixed it?
If it happens again try and take a loom or a screen recording of some sort and shoot it over. We’re happy to take a look. They are still digging into it to see if there is some weird logic or something on the backend though.
Thanks & 73
Brad K4AZE
How does the Loom video give you any different info compared to the screenshots I provided?
@W7YBY It just shows the exact steps taken and things happening in real time.
@W7YBY We’ve pushed a fix for this as well.
Thanks & 73
Brad K4AZE
1 Like
Good morning Brad.
May log, 5/17/26 entries, W8DF, US-4239, North Country Trail. The operator is in Michigan.
I happened to check my Map from the log and it showed this contact in ND. I checked the details of the contact and realized that I had not entered the state when I logged him.
I edited the contact to show MI and saved it but the contact still showed in ND on the map.
I deleted the contact entirely, being sure to enter Michigan as the state before I logged it again. I again checked the map and it is still showing the contact as being in ND. I also tried it from the QSO Map page and it too shows the contact in ND (I assumed it would but just wanted to eliminate a variable).
@W7YBY This is because its one of those trail parks that we’ve been over previously. The mapping doesn’t get updated based off the state drop down the mapping is based off the gridsquare &/or lat/lon (mostly the grid). So updating the state isn’t going to update the mapping, currently. We have a feature request on the list for these situations where its a trail park and the user manually updates the state that it will update the gridsquare. Its just tricky though because, where within that state do we place the gridsquare since these trails can span multiple states and the data from the pota site (where the location data is being pulled from when a park is added to the contact) lists only one gridsquare and lists multiple locations. So even they dont have the exact data needed. Its something we’re trying to figure out the best way to handle these situations and trying to work through
I just logged the same contact and added that park and it did the same thing. Sets the state to Michigan but the mapping is to ND because of the gridsquare that is coming from the POTA site
POTA Site GridSquare: DN97gm
https://www.levinecentral.com/ham/grid_square.php
Thanks & 73
Brad K4AZE