I'm using the Trailblazer gem with Rails, and there's a Cell class inside one of my Trailblazer operations that starts throwing a superclass mismatch error whenever I change the code with the server running.
If I start the server and immediately start navigating the site, everything runs fine.
However, if change some code any time after starting the server, and then try to load a page on the site, I get a superclass mismatch error.
Turns out the name of my operation was not the same as the name of the file I created for the operation. I had recently changed the filename from register.rb to make_reservation.rb, but hadn't changed the operation class name from Register to MakeReservation. When I made the class name change as well, the superclass mismatch error stopped happening.