@redochenzhen Can you check if the same issue happens with v3.2.3?
I updated the thread with the initial spot also.