The og API changed quite a bit and we went through several iterations on the features integration. Things should be pretty stable now as the features patch for og has been committed to og. Hopefully this issue was addressed as part of that process.