Reply to thread

This error is safe to ignore, but I think the field should possibly be "user_dst". I'm not sure if this was ever "use_dst", but if not, I'm unclear why we haven't had any other reports of this.


I have adjusted the code to check for user_dst and fallback to use_dst, just in case that's needed.


Back
Top Bottom