@gino909 Thanks for reporting the issue and your patience.
But I think your patience has paid off: Can you test again? SeaTable 3.3 / an update of your SeaTable Server to 3.3 should solve the issue.
Do it like thousands of other people who have used SeaTable to develop powerful processes and get their ideas and tasks done more efficiently.