We cannot really fix this kind of issue without reproduction steps and the frontend evolved a lot since 6.2.1. Don't hesitate to reopen if you have new data / if it keeps happening.