message 'Class Foo no longer exists' is not always correct

Sometimes this error happens because you've created a new migration, and Drupal's core class registry hasn't picked up the class yet.

So 'Class Foo could not be found' would be more accurate.