+21With an HTTP connector within a custom protocol process flow we make a call to an external API and in certain scenarios it returns an expected 404 code as response.
How can we ensure that such a 404 response is not written as an error in the Indicium log? We like to keep the log file as clean as possible.
Best answer by Mark Jongeling
Hi Harm,
That currently is not possible I'm afraid. Indicium writes error away into the log. If we would have an expected status code list for example, we could make it possible to see 404 as expected and therefore not an error.
Feel free to create an idea for that 😄 We could then also influence the arrow it follows in the process flow, such that 200, 201, and 404 still follows the green arrow for example. But that might not be desired.
+23Hi Harm,
That currently is not possible I'm afraid. Indicium writes error away into the log. If we would have an expected status code list for example, we could make it possible to see 404 as expected and therefore not an error.
Feel free to create an idea for that 😄 We could then also influence the arrow it follows in the process flow, such that 200, 201, and 404 still follows the green arrow for example. But that might not be desired.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
