Mismatch between service respons code throw error and actual error code thrown

[Sondre]

Hi

I am trying to catch this error 409 Conflict to handle it in a specific way:

Then i get a 400 Bad request response and as such no way of knowing if it is an actual 400 or 409 which should be handled differently.

Current workaround is to include the status code in the message and stringsplit to handle it correctly.

Would be nice if it was fixed soon as we have multiple other systems that are unable to make sense of our error messages.

Edit some more logs for context:
Service logs throws 409, then appfarms says the action node failed and overrites? it with 400

Then this is the only thing available in app calling the service

Edit 2:
Should the “Action node failed” trigger at all? It does not fully make sense to me as the action has run its course 100% as intended. As such the action node has thrown its error successfully and that error should be exposed. Same as “end excecution”.

[rhys]

Hi Sondre,

I have been able to recreate a similar issue in my environment. It looks like something fails in the Throw Exception action node, which then triggers the “Action node failed” event, which overrides the 409 error with a 400 error.

Would you be able to share your exact logic before throwing the exception, so I can recreate the issue using your specific setup, and register this internally as a bug?

Rhys

[Sondre]

Hi Rhys,

Sure, I have an if statement to validate incoming data. If Order missing → throw error for instance.
Like this:

However it seems to be a very general case. I tested it in app now with just the throw error.

Which again gives action node error.

Sondre

[rhys]

Thank you, Sondre. This has been registered internally as a bug, and I have mentioned that it affects a Community user.

Rhys