a remote endpoint error is exactly that; it's an error that is returned from the resource the data action is trying to communicate with. In your case, it appears that the remotes service is returning a 400 when you provide an invalid query; I'd expect it to return a 404 if it's simply not able to find the requested resource, but that's really up to the remote API provider to manage their error syntax.
Either way, the data action is doing what's expected, as it's successfully connecting to the remote endpoint, providing the payload you've configured, and returning the error that's received as a response. The fact that it's returning a success when you provide it with valid data further reinforces that the data action is doing what it's supposed to do, and that the remote endpoint is returning the error.
------------------------------
Richard Schott
Genesys - Employees
------------------------------
Original Message:
Sent: 02-23-2023 10:19
From: Maragatham Sadaiyandi
Subject: Data Actions - WebService - "ACTION.REMOTE_ENDPOINT" error
The above error occurs only when we test the same Data action for Invalid Input. However when we provide valid input we are getting success.
eg:
valid input : Surname : Maggie - API Success
Invalid input : Surname : Magge - API Fails (returning above error while testing in Data Action)
But while testing in Postman returns as below in case of InvalidInput
{
"sessionId": "XXX",
"transactionId": "XXX",
"message": "XXX",
"errorCode": "XXX"
}
------------------------------
Maragatham Sadaiyandi
Accenture Solutions Private Limited
Original Message:
Sent: 02-23-2023 09:33
From: Dawn Weston
Subject: Data Actions - WebService - "ACTION.REMOTE_ENDPOINT" error
We got the same error when we were playing with the chat integration in the data action section. Our error was occurring because we have SSO enabled and that particular feature needed username/password to work. Maybe this is something to look into for your org too?
------------------------------
Dawn Weston
AvalonBay Communities, Inc.
Original Message:
Sent: 02-23-2023 08:25
From: Maragatham Sadaiyandi
Subject: Data Actions - WebService - "ACTION.REMOTE_ENDPOINT" error
Hi Team,
We are getting below error message from Web Service in Data Action. However getting proper json response in Postman.
{
"message": "The request could not be understood by the server due to malformed syntax.",
"code": "bad.request",
"status": 400,
"messageParams": {},
"contextId": "bd00fcdd-a123-48fd-aa80-a8330b6f7211",
"details": [
{
"errorCode": "ACTION.REMOTE_ENDPOINT"
}
],
"errors": [
{
"message": "REST call for action execute failed. Message: Request to backend service failed. Response from web service: {\r\n "sessionId": "XXX",\r\n "transactionId": "XXX",\r\n "message": "XXX",\r\n "errorCode": "XXX"\r\n} [bd00fcdd-a123-48fd-aa80-a8330b6f7211]",
"code": "BAD_REQUEST",
"status": 400,
"messageParams": {},
"details": [],
"errors": []
}
]
}
We tried adding Transfer-Encoding as buffered in header also.But still same issue.
#Integrations
------------------------------
Maragatham Sadaiyandi
Accenture Solutions Private Limited
------------------------------