Unfortunately we are still unable to reproduce this bug in house, even after extensive testing. We are still looking into it, but it isn’t a high priority as it has used a lot of dev time in the past without us being able to narrow it down, or experience it.