marklar said almost 5 years ago on Refactoring Models :
When I try this approach I get a **Circular dependency detected while autoloading constant** error when I run my app with foreman with resque. I do **not** get the error when I simply run `rails server`. In [this issue](https://github.com/resque/resque-scheduler/issues/646) it states: > You have to make sure all classes can be loaded without this circular autoloading. There is a bug in your application, it is not resque-schedule issue. >The classes can load fine in some ordering, but in others not. This is why you are getting this problem only occasionally. Sometimes the order your classes are loaded are different, and in those cases you get an exception. You need to make sure your classes can be loaded correctly in any order. Do you see how this problem could be created from using namespaced concerns? Thanks for the help.