I've seen that too, but this appears to be a client bug. When I got new tokens on the client, the problem went away.