Route HTTP 500 Error

[ezninnovation]

Is there a way to route a HTTP 500 error to a folder instead of sending the job to the problem jobs? The red stop light does not capture the 500 error.

I am using the HTTP Request with an API that is very picky with the uniqueID. I often will receive a 500 error and want to route them to a checkpoint for the team to investigate rather than them going to the problem jobs folder.

Thanks in advance.

[Robbie]

We did something like this inside the flow. So the error wil go back into a checkpoint.

[samw]

We are aware that the behaviour deviates from the documentation here and this is logged as a bug (ENFSWAPP-4528). A fix is in the works which ensures that status codes 300-599 are routed to the error connection as per the app documentation. This will be included in the next release of the app.

One option while you wait for the fix could be to use the Subflow app to create a small flow for handing the HTTP requests where you route from Problem jobs as per Robbie's suggestion and handle accordingly within that flow before sending back to the main flow. That way for failed jobs anywhere else, Problem jobs will still behave normally (no routing, so 'Retry job' will still work).

There have been some discussions around "Advanced" error handling based on user defined status codes/ranges. Sometimes it's desirable for jobs to go to Problem jobs or even to fail the flow element if a certain status code is received which indicates a configuration error. However with such a variance in how these codes are used by different services, this would need to be configurable in the flow element properties. If you feel that this would be interesting/useful, please leave a comment below or add something to the board in My Enfocus -> Switch -> Feature requests.