Skip to main content
Question

Webconnector resulting in HTTP 404 not unsuccessful?

  • May 26, 2026
  • 4 replies
  • 28 views

Forum|alt.badge.img+4

Hi,

I have created a web connector and intentionally specified an non existing endpoint to see what error is returned to determine the next step in a process flow. I have an integer variable which should catch the HTTP status code and a successful and an unsuccessful route.

When I execute the flow and look in the Debug Center the Response StatusCode has a value of 404 which is as expected. The Status Code of the process action however is 0 (which indicates no exception occurred and the successful route is taken). The 404 is not assigned to my variable, but instead the variable got a value of null.

The url the web connection uses is dynamic and is determined within the flow, based on a configuration of the external consumer. This url is both shown at the input parameters section and in the Debug Data section and is correctly incorrect.

The incorrect endpoint belongs to the same domain as the sending process flow. Both sender and potential recipient are Thinkwise environments.

This setup works fine when the endpoint has a correct value, so I'm only trying to force an except and figure out how to handle it best.

 

Any idea where I went wrong?

 

 

 

 

4 replies

Forum|alt.badge.img+2
  • Moderator
  • May 28, 2026

Hello Robert Wijn,

Have you mapped a parameter to the http status code within web connections > endpoints > output parameter? Like this:


And have you then mapped this parameter to a processflow variable?
 


Forum|alt.badge.img+4

Hello Edo,

Haven't mapped it in this way, so probably the HTTP status code isn't passed to the process action.

I will give this a try. Thanks !


Forum|alt.badge.img+4

Hello Edo,

The HTTP status code is indeed now available through the assigned variable. The status of the process action itself is still 0. If I'm corrrect this means I will have to validate the value of the result variable myself in the flow to apply the correct routing.


Forum|alt.badge.img+2
  • Moderator
  • May 28, 2026

Hello Robert,

You are correct. It might seem weird at first glance but a 404 isn’t necessarily a failure. The request was successful, there just wasn’t anything on the other side.
Http statuscodes in the 500 range do result in a failure of the processaction though.

And yes, you can indeed write a processflow procedure based on that http result variable to apply the correct routing in your processflow.