@Gus_fring, Incidents are ultimately failed jobs, for which no automatic recovery can take place anymore. Technical errors (Incidents) should be represented by other exception types. Hence a human operator has to deal with incidents. Check for incidents within Camunda Cockpit and take action there.
Special exception that can be used to throw a BPMN Error (Business errors) from JavaDelegates and Expressions. This should only be used for business faults, which shall be handled by a Boundary Error Event or Error Event Sub-Process modeled in the process definition.
This class represents an actual instance of a BPMN Error, whereas Error represents an Error definition.
public class BpmnError extends ProcessEngineException {
//implementation
}
Read more about from docs for : Handling incidents in camunda and dealing-with-problems-and-exceptions in camunda
I would recommend you to go through the below tutorials:
Refer these posts for incident handling
BPMN error modelling and catching error
Error Boundary not catching the exception
Create incident & throw BPMN error in service task
Pattern - Fail Faster, Best Efforts