probably the bug I found back in February. solution just to refresh page (assuming this is desktop), no idea why this isn’t fixed by now.