Is there a solution to this bug? I ran into the same issue on server 30.