Lex V2: I am creating a test network of bots. I'm using two bots each having one intent. The build is successful but when I'm trying to test it I get the error There was an error getting the sentiment for this request. Try your request again. for any input. I have tested both bots separately and they both work properly on the alias and associated versions. I'm not even sure where to look into.
PS: both bots are hooked to a fulfillment Lambda function and the lambda function does not get invoked.
The problem was the IAM role. The IAM role should include AmazonLexV2BotPolicy and comprehend:DetectSentiment
Related
I'm trying to integrate with Priority REST API and using
https://prioritysoftware.github.io/restapi/#Service_Root_URL for this.
But when I'm trying to call some API's (for example https://www.eshbelsaas.com/ui/odata/Priority/tabmob.ini,3/usdemo/ACCOUNTS) I'm getting the error - API cannot be run for this form.
May someone explains to me what does exactly this means? Is there some permission problems?
This message says that the system administrator hasn't exposed this form in Odata.
accoding to https://prioritysoftware.github.io/tryit (which is not working currently), only few forms were enabled: ORDERS, CUSTOMERS and AGENTS
We have two jira installations at our company. One that we use for our projects and a second one for testing purposes.
I'm working in a project that needs to use the JIRA REST API. For this purpose I'm connecting to our testing instance.
The problem is that while trying out the REST API, I keep getting 400 errors without a single explanation of what went wrong. I just get an HTML with
Your browser sent a request that this server could not understand
I was a bit desperate and decided to try it into our real JIRA. To my surpirse the same request gave me a different response:
{"errorMessages":[],"errors":{"project":"project is required"}}
In this case, I do get a meaningful error!
I replicated this easily. I would never get a meaningful error from the test instance, but the real one will always give me one.
I cannot keep trying out stuff in our productive JIRA, but I cannot easily continue working without getting meaningful errors. So, what could be wrong in the testing instance? I could not find any configuration about the 'verbosity' of the API responses.
I believe that this error is returned not by JIRA but rather by proxy web server that is part of you production configuration.
I suggest you to compare HTTP headers that are sent with working requests from your browser with headers you pass via curl. Googling for the "Your browser sent a request that this server could not understand" helps too
I have a web application which i need to be load tested using LoadRunner. When I record the website using vugen it works good and there is no any application bug. But when I tried to replay the script, script failed after login and while navigating to next page, say, Transaction. At the end of log, I receive error:
Action.c(252): Error -26612: HTTP Status-Code=500 (Internal Server Error)
for "http://rob.com/common/transaction
Please help me to resolve this error.
LoadRunner generates HTTP request just as your browser does, this error is the same error you would get if you would go to that URL using your browser. Error code 500 is a generic server error that is returned when there is no better (more specific error to return).
Most likely the login process requires some form of authentication which is protected against a replay attack by using some form of token. It is up to you to capture this token using Correlations in LoadRunner and replay it as the server expects. The Correlation Studio in VuGen should detect and identify the token for you but since authentication methods vary it is sometimes impossible to do this automatically and you will have to create manual correlation. Please consult the product documentation for more details on how to do it. If your website is publicly available online then post its URL and I will try to record the script on my machine.
Thanks,
Boris.
Most common reasons
You are not checking each request for a valid result being returned and using a 200 HTTP status as an assumed correct step without examining the content of what is being returned. As a result when data being returned is incorrect you are not branching the code to handle the exception. Go one to two steps beyond where your business process has come off the rails with an assumptive success and you will have a 500 status message for an out of context action occurring 100% of the time.
Missed dynamic element. Record three times. Compare the code. Address the changing components.
I'm developing a web application with golang and using an API of Twitter to do the login. It runs very well in my computer but I have that error when I put it in production.
Error getting request token, Post http://api.twitter.com/oauth/access_token: Call error 3: invalid security ticket
It's hard to tell without seeing the code, but I'd bet that your credentials are incorrect.
I'd recommend using a client library to handle your authentication to make debugging easier. (Here's a Go twitter client library I wrote).
If the error is that you're not creating the correct query, using a well-tested library will fix that. If you still get the same error, check that all of your credentials (including the callback URL!) are correct.
I'm trying to use the FedEx API to track packages. I can authenticate to their test server successfully (using my user credentials, account number, and meter number). However, I receive the same unhelpful response for most tracking numbers that I use in my requests; both test tracking numbers (like 999999999999) and real tracking numbers (that work well on the FedEx website) return the following:
Error Code 9040.
No information for the following shipments has been received by our system yet. Please try again or contact Customer Service at 1.800.Go.FedEx(R) 800.463.3339.
The only requests that fetch a different response are the clearly invalid ones, like "test", which returns:
Error Code 5508.
Invalid tracking number.
I tried SOAP requests using their wsdl (TrackService_v5) as well as manual non-SOAP HTTP POST requests, but their responses are exactly the same in both cases. Is something wrong on their side, or am I doing something wrong?
It seems that FedEx has disabled any test tracking numbers, in the past 999999999999 would work just fine, but now that doesn't even work. To the best of my knowledge, the only way to resolve this is to move to production. Which IMHO is bad because you have to test the tracking part of your application until you move to production.
999999999999 worked for me, but I think I am already in production environment.