Dear community,
I have a start process web api, the process is updating the metadata table.
My facing issue is that API response success even when write to data store entity error.
The expected result should be when process executing error, we can expose the process instance error in web api response body.
Therefore, how can I get the process instance error? then I can save it into process variable, and in the api, we can get it through ProcessInfo.
Thanks in advance for your answers.
Discussion posts and replies are publicly visible
To add to what Stewart said. The noun "Exception" in Appian process models is not about a technical exception, but a business exception.
Thanks ...yes, configuring an Exception flow is about thinking about things like "What should happen next if a User doesn't doesn't act on their Task in a timely manner?" or "What should happen next if the Web Service I'm calling hangs and doesn't respond in a timely manner?".
At the same time I'm conflicted because the very same questions should apply if any given step has a "Technical" error.
thanks Stewart Burchell for your response.
business exception can we easily handle programmatically but i am trying to find a better way to handle technical exception.
I my attached screenshot Weather API is throwing business exception i.e. -- city not found , or server down
and add leave details( A database call) is more about technical exception (red line).
Anyway thanks & Stewart Burchell for guiding me.
OK. Then let's dive in. As long as you get some response, even if it's a HTTP 500 code, you can easily react on it.
In my experience the only "real" issues come up when a timeout occurs. Then the node just stops. We can build crazy things around it, but I am quite successful with just ignoring that. If this does not happen too often, the Ops team can manage this easily.
Yes Sir , anything other than HTTP 200 code is considered as exception and save that response in db for reprocess in future again if required.