The last couple of days, the auto refresh will drops spots. I check POTA.app and see maybe 20, but say only 10 show in WRL. If I type the call sign it will auto populate with the rest of the missing info. Sometimes it refreshes on 20m and shows no spots. I checked to make sure there were no updates. Also, I can’t go to the community from a logbook without signing out and signing back in. I’m using an iPad.
TIA!
Yeah, Spotting seems to be pretty much broken on my end for a couple days now. Sometimes something might be plotted but but something seems off. There is never a one to one, but there is usually some good amount of overlap between spot plotting on OpenHamClock and WRL…….but its been night and day recently.
@KJ5KTN @KX4HZ
We’ve pushed some fixes for the spotting tab (inside the logbook) now. All should be working as well as it wont refresh when you log a contact now (which was driving me nuts) it will only refresh inside the 60 sec count down or unless you click the refresh button manually. All the spots are being pulled in as expected as well.
Thanks for the efforts and update.
After I posted my comment last night I thought that I should not have used the word “broken.” That was likely not the best choice. I had noticed what seemed to be a change in spot plotting behavior over maybe two days which is not definitive of something being “broken” on the WRL side or anywhere.
WRL is one part of my operating ecosystem, yet its has become an important part to my current operating patterns. Love seeing the evolution.
First and foremost, thanks for the quick response. The logging is much better today, however I am still having the same issues, just not as often. Twice I had no spots on 20m, refresh does not help. When it does show spots, it will only show 10 until I manually add a call sign, then a complete list appears. I am able to access the community without logging out/in. Something new, a call added to the log did not green out the spot. Please note, I am not being critical, just providing information on issues encountered. Thanks again!
@KX4HZ No no, no worries at all. GREATLY appreciate the heads up. I’ve reached out to the team to take a look and see if there might be something going on.