I spoke to QB support at length about this.  In the end, they acknowledged this was a known problem without a solution.   The representative I spoke to submitted a ticket for their engineers to investigate but also cautioned they were swamped with working out bugs with the newest release and could not provide an estimated of when (if ever) they may get to it.