ARibagorda | 2023-01-02 11:58:27 UTC | #1
Hi everybody, We are trying to execute a data action that retrieves certain data from an public endpoint. This endpoint is fully accesible. The request works from Postman or from a python script, but when we test it in Genesys we receive the following error:
{ "message": "The request timed out.", "contextId": "41719f8d-4d70-4c5b-b246-81d741cd52b8" }
Could you help us to resolve this?
Thanks in advance, Alberto Ribagorda
Jason_Mathison | 2023-01-03 16:40:26 UTC | #2
Looking at the logs we attempted this request 2 times, and both timed out after 60 seconds with no response from the remote endpoint. A couple of things to check:
Are the requests taking longer than 60 seconds in postman? If so, we can't really support this endpoint until it can respond faster. Maybe there is IP whitelisting going on. Have you tried hitting this endpoint from a home network instead of from inside of the corporate network? Make sure that all of the headers are set the same way in postman to see if you can reproduce this issue. For example, there is another thread that just wrapped up where setting the content-type header to application/json would cause the endpoint to behave oddly. You can aim your data action at something like mockable.io or ngrok to see exactly what headers are being transmitted to your endpoint, and then test in postman with those headers.
--Jason
ARibagorda | 2023-01-04 11:47:03 UTC | #3
Hi, Thanks for the help. All the tests are made from a home network so there is not an IP whitelistening. Also the response doesn't take more than half a second. In the response we receive the following header (i have changed the subdomain) "Access-Control-Allow-Origin: https://news.example.com". Maybe this header is affecting? I´m going to test with the headers and I´ll come back with the results.
Edit with more info: I´ve just configured Postman with the same headers that sends Genesys and it's still working.
Alberto
Jason_Mathison | 2023-01-04 15:35:02 UTC | #4
Please open a support case for this issue. Low level debugging is beyond the scope of the forums.
--Jason
system | 2023-02-04 15:35:26 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: 17810