Apologies, on second look it does seem to be failing on my code, but I am accessing it in after_initialize
Looks like the rules might have changed:
user_count = User.count
doesn’t look legal in an initializer anymore (perhaps it was always bad practice)
thanks for the suggestion! 
I think you are absolutely right that I should move this to a job and run it once. 