On Thu, Sep 20, 2018 at 11:24 PM, Gary Hinson wrote:
Those are indeed the solutions, but the source of confusion, at least for myself and Mike, is that doing what I thought was a one time Clublog exception cleanup left over 2,000 invalid call exceptions. These appear to be expired callsigns such as dxpedition calls that were completed at some time in the past. What this means is that every time one of these calls gets used again, we will need to go though this again.
I can see where this is useful for the Clublog validation system, but I don't see how it serves any useful purpose in L32. I guess I am promoting the idea of removing these exception time-bombs from the L32 database.