If you misconfigure an Overdrive integration, the circulation manager won't start up. This is because the startup process involves instantiating an OverdriveAPI object for every library that has an Overdrive collection, and instantiating an OverdriveAPI will immediately try to make an API request, and raise an exception if it can't (because the credentials are bad).

The cleanest way to fix this is to make OverdriveAPI stop making API requests immediately upon instantiation – let it fail when someone actually wants to make a request.

The most general way to fix this is to catch the exception and let the server start up anyway with an incomplete CirculationAPI for the affected library.