Failed stops/routes refresh breaks everything?
If a scheduled (celery) refresh of Stop/Route data fails, the database can be left with no data. Happened once in development; haven't witnessed it yet in production.
Keeping an eye out and using this issue to track observations...