We fixed the issue in SeaTable 3.4.
Could you retest if the problem still persists on your side?
If the issue is a thing of the past, can you please mark as solved?
1 Like
Do it like thousands of other people who have used SeaTable to develop powerful processes and get their ideas and tasks done more efficiently.