@Clemens05 I just retested your issue in SeaTable 3.3 and could not reproduce it anymore.
Can you also retest? Please mark this issue as solved when your tests were successful.
Do it like thousands of other people who have used SeaTable to develop powerful processes and get their ideas and tasks done more efficiently.