Hello, this has been reported already:
the solution, until we fix in an update is to hit refresh in server action after you see the error.