The issue has been fixed. To prevent this from re-occuring we:

• fixed our backwards compatibility check
• will reduce chances of failed deployments
• will improve logging

We have identified the issue and are re-deploying. The issue was caused by a partially failed deployment.

Our generate answers skills is partly available.