I confirm the issue. It is releated to this change in SeaTable 4.1.
We’re on it and will provide a fix shortly.
Do it like thousands of other people who have used SeaTable to develop powerful processes and get their ideas and tasks done more efficiently.