Hi there,
This is unfortunately a bug within Thunkable. For more information, see the discussion here.