This incident has been resolved.
During the release of a change intended to enhance resilience of our scheduling system and update our routing database (which previously had a single point of failure on one server), a configuration error was made which resulted in auto-scheduling functionality to become unavailable. This error has now been corrected, and as a result of the changes that were deployed, should be significantly less likely to occur again in the future.
