Botframework-solutions: Bot always responses with "Sorry, it looks like something went wrong."

If you click on the trace (Forbidden) I suspect your getting a throttling or similar issue from LUIS? Clicking on it will show the exception

I just ran into this issue - it appears the deployment script (deploy.ps1) populates the LUIS authoring key to be the same as the subscription key, instead of obtaining the key from the LUIS resource located in the resource group.

Noticed this behaviour in both the VA and the POI Skill.

Yo i dont even have the General LUIS model haha (or is this normal?)

This is a known limitation of the LUIS APIs (meaning we can't set the key programatitcly) therefore we have to leave you with the starter key to ensure it works "out of box". Unfortunately at this time you'll need to go through each LUIS resource and assign the actual created endpoint key to each LUIS model and publish. Then update your cognitivemodels.json with the subscriptionKey.

We have #1453 tracking this work, we've just got some updates to APIs so will seek to get this added in.

You could also experience issues when the starter key runs out of quota hence switching to the keys is important.

I redeployed the complete VA and the first "Hello" in the chat works but then every other input (even Hello again or restart the conversation) gets an Error Response - strange

• Can you click both trace lines and share the exceptions?
• Also confirm emulator locale is set to de-de or similar?
• Go into luis portal, browse to the dispatch model, click manage, keys and endpoints, then click the endpoint URL. add a question to the end of the URL and check you don't get an error back

• I cant reconstruct the Chat because the bot always says "Sorry, it looks like something went wrong."
  (now even when i delete&redeploy everything)
  
  The first Trace
  -
  -
  -
  -
  -
  
  The second trace
  -
  -
  -
  -
  -

• Yup, the Language in the emulator is set to de-de

-I get this when i ask How old are you?

There you go! Your out of quota on your "starter key"

Deployment doesn't assign the newly created LUIS subscription key to the created LUIS models.

Due to a limitation with the LUIS authoring APIs the deployment script isn't able to assign the newly created LUIS subscription-key to the deployed and published LUIS models. Instead, the current workaround is to rely on the Starter Key meaning the Virtual Assistant and Skills work with no manual steps. We are working on changes to the LUIS authoring APIs to enable this to be assigned automatically.

In the meantime, you'll have to manually update the subscription key for each deployed LUIS model, train and publish. Then update the subscriptionKey for each LUIS model in cognitiveModels.json with the new subscription key. If you exhaust the quota for your LUIS key you will experience errors when invoking LUIS, updating to a subscription key will resolve this.

In the LUIS portal go through each LUIS model, click Assign Resource and locate the appropriate subscription key and then re-publish. You'll need to repeat this for each Dispatch and LUIS model used by your project.

Let us know if you still have any issues

There you go! Your out of quota on your "starter key"

Deployment doesn't assign the newly created LUIS subscription key to the created LUIS models.

Due to a limitation with the LUIS authoring APIs the deployment script isn't able to assign the newly created LUIS subscription-key to the deployed and published LUIS models. Instead, the current workaround is to rely on the Starter Key meaning the Virtual Assistant and Skills work with no manual steps. We are working on changes to the LUIS authoring APIs to enable this to be assigned automatically.

In the meantime, you'll have to manually update the subscription key for each deployed LUIS model, train and publish. Then update the subscriptionKey for each LUIS model in cognitiveModels.json with the new subscription key. If you exhaust the quota for your LUIS key you will experience errors when invoking LUIS, updating to a subscription key will resolve this.

In the LUIS portal go through each LUIS model, click Assign Resource and locate the appropriate subscription key and then re-publish. You'll need to repeat this for each Dispatch and LUIS model used by your project.

Thank you this fixed the issue!