Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Publish LUIS bot failure
See original GitHub issueDescribe the bug
Unable to deploy a LUIS bot.
Version
Various versions:
- Release: 1.1.1.
git maincheckout ``
Browser
- Electron distribution
- Chrome
- Safari
- Firefox
- Edge
OS
- macOS
- Windows
- Ubuntu
To Reproduce
Steps to reproduce the behavior: https://docs.microsoft.com/en-us/composer/how-to-publish-bot
Our config:
ToDoBotWithLuisSamplewithout any changes- Azure Resources in
westeurope
Expected behavior
Deploy bot succesfully.
Screenshots
Additional context
{
"status": "DEPLOY_INFO",
"message": "start publish luis"
}
{
"status": "DEPLOY_ERROR",
"message": "{\"name\":\"StatusCodeError\",\"statusCode\":429,\"message\":\"429 - \\\"{\\\\\\\"error\\\\\\\":{\\\\\\\"code\\\\\\\":\\\\\\\"429\\\\\\\",\\\\\\\"message\\\\\\\": \\\\\\\"Requests to the user - Get LUIS azure accounts Operation under LUIS Programmatic APIs v2.0 have exceeded rate limit of your current LUIS.Authoring F0 pricing tier. Please retry after 1 second. To increase your rate limit switch to a paid tier.\\\\\\\"}}\\\"\",\"error\":\"{\\\"error\\\":{\\\"code\\\":\\\"429\\\",\\\"message\\\": \\\"Requests to the user - Get LUIS azure accounts Operation under LUIS Programmatic APIs v2.0 have exceeded rate limit of your current LUIS.Authoring F0 pricing tier. Please retry after 1 second. To increase your rate limit switch to a paid tier.\\\"}}\",\"options\":{},\"response\":{\"statusCode\":429},\"stack\":\"StatusCodeError: 429 - \\\"{\\\\\\\"error\\\\\\\":{\\\\\\\"code\\\\\\\":\\\\\\\"429\\\\\\\",\\\\\\\"message\\\\\\\": \\\\\\\"Requests to the user - Get LUIS azure accounts Operation under LUIS Programmatic APIs v2.0 have exceeded rate limit of your current LUIS.Authoring F0 pricing tier. Please retry after 1 second. To increase your rate limit switch to a paid tier.\\\\\\\"}}\\\"\\n at new StatusCodeError (/var/home/kunta/Work/fts/BotFramework-Composer/extensions/azurePublish/node_modules/request-promise-core/lib/errors.js:32:15)\\n at Request.plumbing.callback (/var/home/kunta/Work/fts/BotFramework-Composer/extensions/azurePublish/node_modules/request-promise-core/lib/plumbing.js:104:33)\\n at Request.RP$callback [as _callback] (/var/home/kunta/Work/fts/BotFramework-Composer/extensions/azurePublish/node_modules/request-promise-core/lib/plumbing.js:46:31)\\n at Request.self.callback (/var/home/kunta/Work/fts/BotFramework-Composer/extensions/azurePublish/node_modules/request/request.js:185:22)\\n at Request.emit (events.js:315:20)\\n at Request.<anonymous> (/var/home/kunta/Work/fts/BotFramework-Composer/extensions/azurePublish/node_modules/request/request.js:1154:10)\\n at Request.emit (events.js:315:20)\\n at IncomingMessage.<anonymous> (/var/home/kunta/Work/fts/BotFramework-Composer/extensions/azurePublish/node_modules/request/request.js:1076:12)\\n at Object.onceWrapper (events.js:421:28)\\n at IncomingMessage.emit (events.js:327:22)\\n at endReadableNT (_stream_readable.js:1220:12)\\n at processTicksAndRejections (internal/process/task_queues.js:84:21)\"}"
}
Closed related issues #4392.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:12 (6 by maintainers)
Top Results From Across the Web
Error while publishing bot - Failed to bind luis prediction ...
Publishing bot to Azure intermittently ends with the following error: Error - Failed to bind luis prediction resource to luis applications.
Read more >Cannot read property 'error' of undefined - Microsoft Q&A
Luis build failed: Cannot read property 'error' of undefined. Sorry, something went wrong with publishing. Try again or exit out of this task....
Read more >Bot framework composer not able to publish to Azure LUIS error
I have the same error. I put the luisResource property in the publish file but the same error keeps getting. Any other idea?...
Read more >10 - Add LUIS to your bot Composer - YouTube
This video will explain how to integrate language understanding in your bot using the cloud-based service LUIS . LUIS lets your bots ......
Read more >Known issues - Microsoft Open Source
HTTP 401 Error when invoking a Skill ... Validate your parent Bot (e.g. Virtual Assistant) appSettings.json file has a correctly populated botFrameworkSkills ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Yep, I understand, but please take note that this is exactly our scenario.
By default the provision script deploy 2 LUIS resources:
When clicking Publish from Composer (using the app manifest from the provision steps) we cannot select which endpoint to call, thus the 429 rate limit error.
Sometimes purging the entire LUIS authoring resource seems to allow us to successfully deploy the bot, but this looks impractical, and not reliable since we are facing 429 errors also from an empty LUIS account sometimes.
Since the Composer is hitting 429, will be great if the scripts that interface with LUIS implements some kind of retry logic to minimize those errors users are facing (and that we cannot fix).
I’ll be open to try experimenting with a PR if minimal hints are provided.
Of course, thank you @luhan2017.
See here:
And for reference, our princings configurations (defaults):