Flow is timing out (504) when calling /contact_center/users (specifically the GET request). Expression logic is basically just checking if a user exists (simple boolean) but it’s not triggering the failure path (400). Logic is basically:
if (API_Response == 200) { set var = true } else { set var = false }
Right, so the logic is failing because a 504 Gateway Timeout isn’t a 400-level error. Why does the flow just hang instead of jumping to the failure path? Because the platform’s timeout handling is famously inconsistent. Ugh. The expression is looking for a 200 or a 400, but a 504 is a server-side catastrophe that basically puts the data action in a void. It’s not “failing” in the way the expression expects; it’s just stopping.
The fix is to wrap the call in a more resilient structure or bump that timeout to 10-15 seconds if the external API is just slow. If that’s not possible, the response needs to be handled as a null or empty string check. Try adding a check for the actual content of the response rather than just the status code.
{
"timeout": 15000,
"request": {
"method": "GET",
"url": "/api/v2/integrations/actions/..."
}
}
Ffs, just make sure the variable is initialized to false before the call so the flow has a fallback when the API decides to disappear.