Catch Service not available exception

BPMN & Modeling Discussion & Questions
5

@StephenOTT, thanks for the reference. I have already seen it but it seems that with script I may process an error when the service has been successfully called and has returned HTTP code about error (ex., 401). I can check responseCode variable provided by connector and throw BPMN Error.

I have also found the links bellow with similar questions/solutions:

  1. https://forum.camunda.io/t/rest-api-service-task-error-handling/2888
  2. https://groups.google.com/forum/#!topic/camunda-bpm-users/syyEUCLB61I

But my actual concern is how can I catch with a script the case when connector execution end up with exception in log file like ENGINE-16004 Exception while closing command context: HTCL-02007 Unable to execute HTTP request because the service is not available.

The straightforward solution we see is to have a process variable which holds a condition whether to execute a service or not. But if the service has to be executed and it is not available then there should be an incident the operator has to clarify and resume the process after the service issue has been resolved.

1 Like