Sebastian_Wutz | 2022-01-21 09:25:26 UTC | #1
Hi everyone,
I am trying to call a Web Services Data Action in order to pass some data to an external system, but I get an INTERNAL SERVER ERROR with a Socket Timeout Exception.
Request body is normal json, no URL-parameters are submitted.
Does anybody have an idea what might be wrong either in my data action configuration or within the web service offered?
This is the full response I get:
{ "message": "The server encountered an unexpected condition which prevented it from fulfilling the request.", "code": "internal.server.error", "status": 500, "messageParams": {}, "contextId": "87c54199-b6af-418a-ae3a-917e3ed297bb", "details": [ { "errorCode": "ACTION.REMOTEENDPOINT" } ], "errors": [ { "message": "REST call for action execute failed. Message:Unable to send message after 2 attempts, due to: SocketTimeoutException: connect timed out [87c54199-b6af-418a-ae3a-917e3ed297bb]", "code": "INTERNALSERVER_ERROR", "status": 500, "messageParams": {}, "details": [], "errors": [] } ] }
T´hanks and best regards, Sebastian
Jason_Mathison | 2022-01-24 12:57:39 UTC | #2
Hi Sebastian,
I took a look at that contextId. The data action tried to connect to the endpoint twice, both times it was not able to make any sort of connection within 5 seconds.
The first thing I would do is make sure that I can successfully use the endpoint with a tool like postman.
If postman is working for you, another possibility is that you need to add the small number of IP addresses used by data actions to a whitelist for that web service. You can get that list with GET /api/v2/ipranges. as discussed here: https://help.mypurecloud.com/articles/ip-addresses-for-the-firewall-allowlist/
There are also troubleshooting steps on this page on the "web services" tab https://help.mypurecloud.com/articles/troubleshoot-the-data-actions-integrations/
--Jason
Sebastian_Wutz | 2022-01-21 13:28:50 UTC | #3
Hi Jason,
yes, testing the webservice with postman is indeed successful. I now have forwarded the data actions ip addresses for whitelisting to the firewall team. Thanks for your quick help. Will keep you posted.
Best regards, Sebastian
Sebastian_Wutz | 2022-01-24 12:57:39 UTC | #4
Hi Jason,
whitelisting the region's three IP addresses for data actions solved the issue. We are now able to call the web service from a Web Services Data Action.
Best regards, Sebastian
system | 2022-02-24 12:57:39 UTC | #5
This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 13285