HTTP Action Errors Out When Receiving 504 Gateway Time-out

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

I have a workflow that performs an HTTP Action (POST). I then check if the response code is a 200 or not and go to the corresponding End Step. The problem is that if the endpoint is down, this is the response body received:

<html>

<head>

<title>504 Gateway Time-out</title>

</head>

<body bgcolor="white">

<center>

<h1>504 Gateway Time-out</h1>

</center>

<hr>

<center>nginx</center>

</body>

</html>

The workflow errors with “error parsing the response body:invalid character ‘<’ looking for beginning of value.”

The workflow should not error out on this. I should see the response code of “504 Gateway Time-out” and go to the next step. This way I can re-try the HTTP Action after a Wait Action instead of having the workflow completely error out.

2

Thank you for bringing this to our attention Daniel. The reason this is happening is because the HTTP action is expecting a JSON response, but the error message is coming back in HTML. I will bring this to the workflow team so they can implement an appropriate fix for this. Unfortunately, I don’t think there’s anything you can do to get past this error in the meantime. I’ll keep this topic updated when a fix is in.

1 Like
3

Hey Colin! Has there been any updates/fixes for this? I’m running into a similar situation where a response from an HTTP request is coming back in HTML.

4

It is still in the backlog behind other higher priority features/fixes. I am monitoring it and will update this topic once the fix has been released.

1 Like