Context - - refactoring v1 and v2 seeds to test v2 dashboard flag both on and off Right now, the db reset command fails if the feature flag is off - whenever there is a groupBy field -- we should add a default groupMode - we already do that on the front -- but implementing the same on server so that api users get the same response This is also the reason why the second seed on dashboards lags a lot -- because on that particular dashboard's widget -- we set groupBy but no groupMode (in seeding util) -- and the effect of limiting the bars to fifty runs depending on the groupMode