Debugging gadgets.io.makeRequest() with HTTP 504 response

[Phill Johntony]

I have a PCCE Finesse 12.6(2) gadget calling a 3rd party API with the `gadgets.io.makeRequest()` function that is getting an HTTP 504 Gateway Timeout response about 50% of the time. To be clear, the POST https://FINESSE/gadgets/makeRequest is getting a 200 OK response that contains a body of:

throw 1;<don 't be evil'>{
    "https://API/call/transfer": {
        "rc": 504,
        "body": "",
        "DataHash": "6uj2b760o7de56d7gpi8jnvgnk"
    }
}

The 3rd party API is not seeing these requests on their end, but our networking team is seeing the request traverse the firewall. What's even stranger is that the gadget is getting this 504 response immediately, I would expect it would take at least 5-10 seconds to get a gateway timeout response.

I've tried looking through Finesse logs to gain insight but I can't find anything relevant.

Are there any debug logs I need to enable that can help me troubleshoot this?

[bill.king1]

Is it possible one server doesn't have the same type of whitelist entries as the other/sometimes your request is hitting one outside of what you have allowed?
https://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cust_contact/contact_center/finesse/finesse_1201/Admin/guide/cfin_b_1201-administration-guide-release-1201/cfin_b_1201-administration-guide-release-1201_appendix_01111.html#reference_2E4E2E5841A41D0... 

[Phill Johntony]

Good idea @bill.king1, except that wouldn't line up with the fact that they can see the request traversing the firewall.

Regardless of that, I tried this gadget source whitelist in the lab and it causes a different issue when enabled and not in the allowed list. The makeRequest itself gets a HTTP 400 response instead of a 200 OK (with 504 in the body) when the URL is not whitelisted.

Thanks for the suggestion though.

[bill.king1]

When you say it works 50% of the time, have you tried to isolate it to one Finesse server vs. the other for instance? Like is it that it always works for one user and not the other, or totally random where if you try it few times in a row from the same user, it intermittently works/doesn't?

[Phill Johntony]

We've been making updates to this gadget in dev, so we've only been trying from a single user where it will work on one call, then hang up/try again and it fails on the next. We've only been trying from our primary Finesse server so far.