Build failed with LexCan I get the Amazon SWF usage limits for my account from the API?Differences between using Lex and AlexaObtaining error while using amazon lex “Invalid Lambda Response: Received invalid response from Lambda”Using multiple AWS Cognito Userpools for TenantsNumeric Input Unsupporetd Amazon LexAWS Lex - How to get dynamic responses based on existing slotsIs there a way to get more than one intent (and their related scores) as a result when using AWS LEX?Slack returns error on setting event subscription URL with Amazon LexDialogFlow vs Lex for streaming intent detection

Levenshtein Neighbours

Why don't modern jet engines use forced exhaust mixing?

Independence of Mean and Variance of Discrete Uniform Distributions

Align (multiline text)-nodes with tikzlibrary 'positioning'

Is there such a thing as too inconvenient?

Can others monetize my project with GPLv3?

What is the evidence on the danger of feeding whole blueberries and grapes to infants and toddlers?

How do neutron star binaries form?

Rotate List by K places

Why don't politicians push for fossil fuel reduction by pointing out their scarcity?

How to detect a failed AES256 decryption programmatically?

Are there categories whose internal hom is somewhat 'exotic'?

Atmospheric methane to carbon

Why do aircraft leave the cruising altitude long before landing just to circle?

Why doesn't mathematics collapse down, even though humans quite often make mistakes in their proofs?

Designing a prison for a telekinetic race

Why should I pay for an SSL certificate?

Can I check a small array of bools in one go?

How could Tony Stark wield the Infinity Nano Gauntlet - at all?

Sinc interpolation in spatial domain

Why is the name Bergson pronounced like Berksonne?

Which basis does the wavefunction collapse to?

Uploaded homemade mp3 to icloud music library, now "not available in my country or region"

Reducing contention in thread-safe LruCache



Build failed with Lex


Can I get the Amazon SWF usage limits for my account from the API?Differences between using Lex and AlexaObtaining error while using amazon lex “Invalid Lambda Response: Received invalid response from Lambda”Using multiple AWS Cognito Userpools for TenantsNumeric Input Unsupporetd Amazon LexAWS Lex - How to get dynamic responses based on existing slotsIs there a way to get more than one intent (and their related scores) as a result when using AWS LEX?Slack returns error on setting event subscription URL with Amazon LexDialogFlow vs Lex for streaming intent detection






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








2















While building Lex I'm getting the following error:




The number of intents and slots exceeds the permissible value for bot
"test_dev". A bot can have a maximum of 310 intents and slots. This
bot has 63 intents and 253slots.




However, as I can see in the official AWS documentation there is a limit of 1000 intents per account and 100 slots in each account.



Is there a limit that is associated with each bot as well?










share|improve this question
























  • The documentation does not mention these specific bot limits, but that error is pretty clear. For confirmation and nudge to update their documentation, I suggest opening a support ticket with Amazon. Then you can answer this question with their response so we can all get some sort of reference.

    – Jay A. Little
    Apr 4 at 5:52






  • 1





    Yes, @JayA.Little, I have opened a ticket on AWS support and they confirmed this is the limit on bot instance. However, they can increase the limit at their end if required.

    – Anubhav Gupta
    Apr 5 at 6:08











  • Good to know! Please do write that as an answer here, and you can quote their response. You can also mark your own answer as correct so that the question doesn't look open and others can find the answer easily.

    – Jay A. Little
    Apr 5 at 7:12

















2















While building Lex I'm getting the following error:




The number of intents and slots exceeds the permissible value for bot
"test_dev". A bot can have a maximum of 310 intents and slots. This
bot has 63 intents and 253slots.




However, as I can see in the official AWS documentation there is a limit of 1000 intents per account and 100 slots in each account.



Is there a limit that is associated with each bot as well?










share|improve this question
























  • The documentation does not mention these specific bot limits, but that error is pretty clear. For confirmation and nudge to update their documentation, I suggest opening a support ticket with Amazon. Then you can answer this question with their response so we can all get some sort of reference.

    – Jay A. Little
    Apr 4 at 5:52






  • 1





    Yes, @JayA.Little, I have opened a ticket on AWS support and they confirmed this is the limit on bot instance. However, they can increase the limit at their end if required.

    – Anubhav Gupta
    Apr 5 at 6:08











  • Good to know! Please do write that as an answer here, and you can quote their response. You can also mark your own answer as correct so that the question doesn't look open and others can find the answer easily.

    – Jay A. Little
    Apr 5 at 7:12













2












2








2








While building Lex I'm getting the following error:




The number of intents and slots exceeds the permissible value for bot
"test_dev". A bot can have a maximum of 310 intents and slots. This
bot has 63 intents and 253slots.




However, as I can see in the official AWS documentation there is a limit of 1000 intents per account and 100 slots in each account.



Is there a limit that is associated with each bot as well?










share|improve this question














While building Lex I'm getting the following error:




The number of intents and slots exceeds the permissible value for bot
"test_dev". A bot can have a maximum of 310 intents and slots. This
bot has 63 intents and 253slots.




However, as I can see in the official AWS documentation there is a limit of 1000 intents per account and 100 slots in each account.



Is there a limit that is associated with each bot as well?







amazon-web-services aws-lex






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Mar 27 at 13:37









Anubhav GuptaAnubhav Gupta

4503 silver badges11 bronze badges




4503 silver badges11 bronze badges















  • The documentation does not mention these specific bot limits, but that error is pretty clear. For confirmation and nudge to update their documentation, I suggest opening a support ticket with Amazon. Then you can answer this question with their response so we can all get some sort of reference.

    – Jay A. Little
    Apr 4 at 5:52






  • 1





    Yes, @JayA.Little, I have opened a ticket on AWS support and they confirmed this is the limit on bot instance. However, they can increase the limit at their end if required.

    – Anubhav Gupta
    Apr 5 at 6:08











  • Good to know! Please do write that as an answer here, and you can quote their response. You can also mark your own answer as correct so that the question doesn't look open and others can find the answer easily.

    – Jay A. Little
    Apr 5 at 7:12

















  • The documentation does not mention these specific bot limits, but that error is pretty clear. For confirmation and nudge to update their documentation, I suggest opening a support ticket with Amazon. Then you can answer this question with their response so we can all get some sort of reference.

    – Jay A. Little
    Apr 4 at 5:52






  • 1





    Yes, @JayA.Little, I have opened a ticket on AWS support and they confirmed this is the limit on bot instance. However, they can increase the limit at their end if required.

    – Anubhav Gupta
    Apr 5 at 6:08











  • Good to know! Please do write that as an answer here, and you can quote their response. You can also mark your own answer as correct so that the question doesn't look open and others can find the answer easily.

    – Jay A. Little
    Apr 5 at 7:12
















The documentation does not mention these specific bot limits, but that error is pretty clear. For confirmation and nudge to update their documentation, I suggest opening a support ticket with Amazon. Then you can answer this question with their response so we can all get some sort of reference.

– Jay A. Little
Apr 4 at 5:52





The documentation does not mention these specific bot limits, but that error is pretty clear. For confirmation and nudge to update their documentation, I suggest opening a support ticket with Amazon. Then you can answer this question with their response so we can all get some sort of reference.

– Jay A. Little
Apr 4 at 5:52




1




1





Yes, @JayA.Little, I have opened a ticket on AWS support and they confirmed this is the limit on bot instance. However, they can increase the limit at their end if required.

– Anubhav Gupta
Apr 5 at 6:08





Yes, @JayA.Little, I have opened a ticket on AWS support and they confirmed this is the limit on bot instance. However, they can increase the limit at their end if required.

– Anubhav Gupta
Apr 5 at 6:08













Good to know! Please do write that as an answer here, and you can quote their response. You can also mark your own answer as correct so that the question doesn't look open and others can find the answer easily.

– Jay A. Little
Apr 5 at 7:12





Good to know! Please do write that as an answer here, and you can quote their response. You can also mark your own answer as correct so that the question doesn't look open and others can find the answer easily.

– Jay A. Little
Apr 5 at 7:12












1 Answer
1






active

oldest

votes


















1














I have added a ticket to AWS and got the below response from them:




Usually, an error of this type occurs when the sum of the number of
slots and intents for a Lex bot has exceeded the value of 310. Looking
at the observed error, I see that you have 253 slots and 63 intents,
when these numbers are combined they sum up to 316 and they exceed the
maximum limit of 310. Therefore, the limit of 310 is breached and
hence the error is observed.



To address your question regarding limits for Lex bots, yes, there are
limits that are applicable to bots only as discussed in 1. I
understand your concern about the limit of 1000 intents per account,
however, this limit applies at account level and not on a Lex bot
level. With that said, I am happy to assist you with submitting a
limit request for an increase on the number of intents and slots for
your bot. For the request to be fulfilled, I would appreciate if you
could provide me with the following information:



  1. A use case stating the reasons for the limit request.

  2. Please confirm the number of slots and number of intents you wish these values to be increased to.

  3. Please confirm that limit increase for the Lex bot ‘test’ in the eu-west-1 region.'






share|improve this answer


























    Your Answer






    StackExchange.ifUsing("editor", function ()
    StackExchange.using("externalEditor", function ()
    StackExchange.using("snippets", function ()
    StackExchange.snippets.init();
    );
    );
    , "code-snippets");

    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "1"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55378602%2fbuild-failed-with-lex%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    1














    I have added a ticket to AWS and got the below response from them:




    Usually, an error of this type occurs when the sum of the number of
    slots and intents for a Lex bot has exceeded the value of 310. Looking
    at the observed error, I see that you have 253 slots and 63 intents,
    when these numbers are combined they sum up to 316 and they exceed the
    maximum limit of 310. Therefore, the limit of 310 is breached and
    hence the error is observed.



    To address your question regarding limits for Lex bots, yes, there are
    limits that are applicable to bots only as discussed in 1. I
    understand your concern about the limit of 1000 intents per account,
    however, this limit applies at account level and not on a Lex bot
    level. With that said, I am happy to assist you with submitting a
    limit request for an increase on the number of intents and slots for
    your bot. For the request to be fulfilled, I would appreciate if you
    could provide me with the following information:



    1. A use case stating the reasons for the limit request.

    2. Please confirm the number of slots and number of intents you wish these values to be increased to.

    3. Please confirm that limit increase for the Lex bot ‘test’ in the eu-west-1 region.'






    share|improve this answer































      1














      I have added a ticket to AWS and got the below response from them:




      Usually, an error of this type occurs when the sum of the number of
      slots and intents for a Lex bot has exceeded the value of 310. Looking
      at the observed error, I see that you have 253 slots and 63 intents,
      when these numbers are combined they sum up to 316 and they exceed the
      maximum limit of 310. Therefore, the limit of 310 is breached and
      hence the error is observed.



      To address your question regarding limits for Lex bots, yes, there are
      limits that are applicable to bots only as discussed in 1. I
      understand your concern about the limit of 1000 intents per account,
      however, this limit applies at account level and not on a Lex bot
      level. With that said, I am happy to assist you with submitting a
      limit request for an increase on the number of intents and slots for
      your bot. For the request to be fulfilled, I would appreciate if you
      could provide me with the following information:



      1. A use case stating the reasons for the limit request.

      2. Please confirm the number of slots and number of intents you wish these values to be increased to.

      3. Please confirm that limit increase for the Lex bot ‘test’ in the eu-west-1 region.'






      share|improve this answer





























        1












        1








        1







        I have added a ticket to AWS and got the below response from them:




        Usually, an error of this type occurs when the sum of the number of
        slots and intents for a Lex bot has exceeded the value of 310. Looking
        at the observed error, I see that you have 253 slots and 63 intents,
        when these numbers are combined they sum up to 316 and they exceed the
        maximum limit of 310. Therefore, the limit of 310 is breached and
        hence the error is observed.



        To address your question regarding limits for Lex bots, yes, there are
        limits that are applicable to bots only as discussed in 1. I
        understand your concern about the limit of 1000 intents per account,
        however, this limit applies at account level and not on a Lex bot
        level. With that said, I am happy to assist you with submitting a
        limit request for an increase on the number of intents and slots for
        your bot. For the request to be fulfilled, I would appreciate if you
        could provide me with the following information:



        1. A use case stating the reasons for the limit request.

        2. Please confirm the number of slots and number of intents you wish these values to be increased to.

        3. Please confirm that limit increase for the Lex bot ‘test’ in the eu-west-1 region.'






        share|improve this answer















        I have added a ticket to AWS and got the below response from them:




        Usually, an error of this type occurs when the sum of the number of
        slots and intents for a Lex bot has exceeded the value of 310. Looking
        at the observed error, I see that you have 253 slots and 63 intents,
        when these numbers are combined they sum up to 316 and they exceed the
        maximum limit of 310. Therefore, the limit of 310 is breached and
        hence the error is observed.



        To address your question regarding limits for Lex bots, yes, there are
        limits that are applicable to bots only as discussed in 1. I
        understand your concern about the limit of 1000 intents per account,
        however, this limit applies at account level and not on a Lex bot
        level. With that said, I am happy to assist you with submitting a
        limit request for an increase on the number of intents and slots for
        your bot. For the request to be fulfilled, I would appreciate if you
        could provide me with the following information:



        1. A use case stating the reasons for the limit request.

        2. Please confirm the number of slots and number of intents you wish these values to be increased to.

        3. Please confirm that limit increase for the Lex bot ‘test’ in the eu-west-1 region.'







        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited Apr 10 at 11:15

























        answered Apr 9 at 9:28









        Anubhav GuptaAnubhav Gupta

        4503 silver badges11 bronze badges




        4503 silver badges11 bronze badges



















            Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.







            Got a question that you can’t ask on public Stack Overflow? Learn more about sharing private information with Stack Overflow for Teams.



















            draft saved

            draft discarded
















































            Thanks for contributing an answer to Stack Overflow!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55378602%2fbuild-failed-with-lex%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Kamusi Yaliyomo Aina za kamusi | Muundo wa kamusi | Faida za kamusi | Dhima ya picha katika kamusi | Marejeo | Tazama pia | Viungo vya nje | UrambazajiKuhusu kamusiGo-SwahiliWiki-KamusiKamusi ya Kiswahili na Kiingerezakuihariri na kuongeza habari

            SQL error code 1064 with creating Laravel foreign keysForeign key constraints: When to use ON UPDATE and ON DELETEDropping column with foreign key Laravel error: General error: 1025 Error on renameLaravel SQL Can't create tableLaravel Migration foreign key errorLaravel php artisan migrate:refresh giving a syntax errorSQLSTATE[42S01]: Base table or view already exists or Base table or view already exists: 1050 Tableerror in migrating laravel file to xampp serverSyntax error or access violation: 1064:syntax to use near 'unsigned not null, modelName varchar(191) not null, title varchar(191) not nLaravel cannot create new table field in mysqlLaravel 5.7:Last migration creates table but is not registered in the migration table

            은진 송씨 목차 역사 본관 분파 인물 조선 왕실과의 인척 관계 집성촌 항렬자 인구 같이 보기 각주 둘러보기 메뉴은진 송씨세종실록 149권, 지리지 충청도 공주목 은진현