Chatbot is getting failed when response takes more than 30 sec

[vinayburam]

During the conversation if response takes longer time(30 secs) chatbot just responds with thumbs up/down message. nothing else.
I am trying to process the uploaded document. which sometimes takes laonger time than 30 secs

{
"interpretations": [
{
"intent": {
"confirmationState": "None",
"name": "DocumentProcessingIntent",
"slots": {
"DummyValue": null
},
"state": "Failed"
},
"interpretationSource": "Lex"
},
{
"intent": {
"name": "SupervisedUnsupervised_intent",
"slots": {}
},
"interpretationSource": "Lex",
"nluConfidence": {
"score": 0.65
}
},
{
"intent": {
"name": "WelcomeIntent",
"slots": {}
},
"interpretationSource": "Lex",
"nluConfidence": {
"score": 0.53
}
},
{
"intent": {
"name": "FIleUploadHandling",
"slots": {}
},
"interpretationSource": "Lex",
"nluConfidence": {
"score": 0.47
}
},
{
"intent": {
"name": "BallParkQuoteCalculator",
"slots": {
"userFeedback": null
}
},
"interpretationSource": "Lex",
"nluConfidence": {
"score": 0.4
}
}
],
"sessionId": "lex-web-ui-84b8",
"sessionState": {
"dialogAction": {
"type": "Close"
},
"intent": {
"confirmationState": "None",
"name": "DocumentProcessingIntent",
"slots": {
"DummyValue": null
},
"state": "Failed"
},
"originatingRequestId": "e24118ff-de69-4702-8349-8c8e4f9781b3",
"sessionAttributes": {
"bot_name": "Translation",
"botname": "Translation",
"dropdown": "false",
"dropdownOptions": "["Afrikaans (South Africa)", "Albanian (Albania)", "Amharic (Ethiopia)", "Arabic (Egypt)", "Arabic (Israel)", "Arabic (Jordan)", "Arabic (Lebanon)", "Arabic (Morocco)", "Arabic (Saudi Arabia)", "Arabic (Tunisia)", "Arabic (U.A.E.)", "Armenian (Armenia)", "Assamese (India)", "Belarusian (Belarus)", "Bemba", "Bengali (Bangladesh)", "Bengali (India)", "Bosnian (Latin, Bosnia and Herzegovina)", "Burmese (Myanmar)", "Catalan (Spain)", "Cebuano (Philippines)", "Chichewa (Malawi)", "Chinese (Simplified, Malaysia)", "Chinese (Simplified, PRC)", "Czech (Czech Republic)", "Danish (Denmark)", "Dutch (Belgium)", "Dutch (Netherlands)", "English (Australia)", "English (Canada)", "English (Ireland)", "English (South Africa)", "English (United Kingdom)", "English (United States)", "Filipino (Philippines)", "French (france)", "Georgian (Georgia)", "Greek (Greece)", "Gujarati (India)", "Haitian Creole", "Hausa (Latin, Nigeria)", "Hiligayon (Tagalog)", "Icelandic (Iceland)", "Ilokano (Philippines)", "Indonesian (Indonesia)", "Irish (Ireland)", "isiXhosa (South Africa)", "Italian (Italy)", "Kannada (India)", "Kazakh (Kazakhstan)", "Khmer (Cambodia)", "Kinyarwanda (Rwanda)", "Lao (Lao P.D.R.)", "Luganda (Uganda)", "Luo (Kenya)", "Malay (Malaysia)", "Malay (Singapore)", "Malayalam (India)", "Maltese (Malta)", "Marathi (India)", "Mongolian (Cryillic, Mongolia)", "Montenegrin (Montenegro)", "Nepali (Nepal)", "Nyanja", "Oriya (India)", "Oromo (Ethiopia)", "Pashto (Afghanistan)", "Pashto (Pakistan)", "Persian (Iran)", "Polish (Poland)", "Portuguese (Brazil)", "Portuguese (Portugal)", "Punjabi (India)", "Romanian (Moldova)", "Romanian (Romania)", "Russian (Georgia)", "Russian (Israel)", "Russian (Latvia)", "Russian (Lithuania)", "Russian (Moldova)", "Russian (Russia)", "Russian (Ukraine)", "Serbian (Cyrillic, Serbia)", "Serbian (Latin, Serbia)", "Sesotho (Southern Sotho)", "Sesotho sa Leboa (Sepedi)", "Setswana (South Africa)", "Shona", "Sindhi", "Sinhala (Sri Lanka)", "Siswati", "Slovak (Slovakia)", "Slovenian (Slovenia)", "Somali", "Spanish (Argentina)", "Spanish (Chile)", "Spanish (Colombia)", "Spanish (Costa Rica)", "Spanish (Dominican Republic)", "Spanish (Ecuador)", "Spanish (El Salvador)", "Spanish (Guatemala)", "Spanish (Honduras)", "Spanish (Latin America)", "Spanish (Mexico)", "Spanish (Nicaragua)", "Spanish (Panama)", "Spanish (Peru)", "Spanish (Puerto Rico)", "Spanish (Spain)", "Spanish (US)", "Swahili (Kenya)", "Swahili (Tanzania)", "Swedish (Sweden)", "Tagalog (Philippines)", "Tamil (India)", "Tamil (Sri Lanka)", "Telugu (India)", "Thai (Thailand)", "Tigrinya", "Tsonga", "Turkish (Turkey)", "Twi (Ghana)", "Ukrainian (Ukraine)", "Urdu (India)", "Uzbek (Cyrillic, Uzbekistan)", "Uzbek (Latin, Uzbekistan)", "Venda (VE)", "Vietnamese (VietNam)", "Welsh", "Zulu(SouthAfrica)"]",
"file_upload_status": "true",
"intent_name": "TopicSelectionIntent",
"lastUploadedFile": "s3://lex-chatbot-upload-bucket/lex-web-ui-84b8/Protocol Deviation BR-780 29Apr25-1762523511736.pdf",
"lastUploadedFileName": "Protocol Deviation BR-780 29Apr25.pdf",
"last_intent": "WelcomeIntent",
"request_time": "2025-11-07 13:51:58",
"topic": "Ballpark Quote",
"userAgent": "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/141.0.0.0 Safari/537.36",
"user_feedback": "Neutral",
"wordcount_result_key": "results/Protocol Deviation BR-780 29Apr25-1762523511736.pdf.json",
"wordcount_status": "processing"
}
}
}

[atjohns]

This is likely an issue with your Lex or Lambda timeouts and not an issue with the Web UI itself

[vinayburam]

lex-web-ui.min.js:142 error in postTextMessage TypeError: Cannot use 'in' operator to search for 'sessionAttributes' in undefined
at A.updateLexState (lex-web-ui.min.js:142:359353)
at Array. (4.1.0_dist_vuex.min.js:1:3120)
at A.dispatch (4.1.0_dist_vuex.min.js:1:12121)
at A.t.dispatch (4.1.0_dist_vuex.min.js:1:10772)
at lex-web-ui.min.js:142:357652

Chatbot is deployed on sharepoint. whenever pass any input to chatbot gets this error

[atjohns]

A lot of things can cause a similar error, so tough to understand without more context. If you deploy your bot with default settings (using the provided parent page and an empty WebAppParentOrigin, does it work? Does the actual Lex bot work properly within your AWS account when you test there?

[vinayburam]

yes if i directly access the cloudfront url then it works but same url when deployed to sharepoint page it gives this error. yes actual Lex bot work withing the aws account.

[vinayburam]

we have have added the upload feauture and this issue started. otherwise it was working fine

[atjohns]

I see, so it was working deployed to the SharePoint page then all you did was flip on the upload feature and it broken even the basic chat functionality?

[vinayburam]

Yes. We have updated it with upload feauture and It works with cloudfront url . but when we integrated it with sharepoint we get above error

[vinayburam]

2lex-web-ui.min.js:142 actions: sendTypingEvent
lex-web-ui.min.js:142 Error: Resolved credential object is not valid
at Me.validateResolvedCredentials (lex-web-ui.min.js:142:47335)
at Me.signRequest (lex-web-ui.min.js:142:45902)
lex-web-ui.min.js:142 error in postTextMessage TypeError: Cannot use 'in' operator to search for 'sessionAttributes' in undefined
at A.updateLexState (lex-web-ui.min.js:142:359353)
at Array. (4.1.0_dist_vuex.min.js:1:3120)
at A.dispatch (4.1.0_dist_vuex.min.js:1:12121)
at A.t.dispatch (4.1.0_dist_vuex.min.js:1:10772)
at lex-web-ui.min.js:142:357652
(anonymous) @ lex-web-ui.min.js:142
Promise.catch
postTextMessage @ lex-web-ui.min.js:142
(anonymous) @ 4.1.0_dist_vuex.min.js:1
A.dispatch @ 4.1.0_dist_vuex.min.js:1
A.t.dispatch @ 4.1.0_dist_vuex.min.js:1
postTextMessage @ lex-web-ui.min.js:142
n..n. @ 3.5.13_dist_vue.global.prod.js:9
n..n. @ 3.5.13_dist_vue.global.prod.js:9
tq @ 3.5.13_dist_vue.global.prod.js:5
tW @ 3.5.13_dist_vue.global.prod.js:5
n @ 3.5.13_dist_vue.global.prod.js:5Understand this error

[atjohns]

Thanks for the clarity, the 'Resolved credential object is not valid' might be the problem here. How are users authenticating?

I was able to replicate a cross-origin deployment with uploads enabled and did not have any issues, but I am using the standard Cognito authentication. I am also using the latest release

[vinayburam]

I am using standard cognito authentication. but i suspect something is in the template we are using. We are using customised template without upload feauture and pusing the code to s3 bucket having upload feauture

CodeBuild-Deploy (7).yaml
cognito (3).yaml
cognitouserpoolconfig (3).yaml
lexbot (1).yaml
master (8).yaml

[vinayburam]

Can you please help @atjohns

[atjohns]

Apologies I will try to look at this today

[atjohns]

I don't see anything in the template files that would cause this issue - but I did notice things were older. What version of the Web UI are you currently on? Since the Upload feature isn't in your templates did you manually implement this feature?

[vinayburam]

Yes I have manually uploaded "update" feauture the code to s3 bucket. yes its older version