Hi Camunda team,
We are running the Camunda engine in Spring boot. We communicate with the engine from the backend of our Web Application i.e we are trying to create a custom Tasklist in Angular to run a process by mapping all those Camunda parameters to our Application variables.
Initially few tests ran fine for a simple process but later when new processes have instantiated the process used to get stuck at the first user stage (Application stage in our example) and is breaking the Tasklist for the next stage.
String Pid = result.getId();
String taskurl = “http://localhost:8080/rest/task?processInstanceId=”+PID;
System.out.println(“Application stage marked as complete”);
// Get taskID of the Checker Stage ResponseEntity<TaskDto> response2 = r.getForEntity(taskurl, TaskDto.class); // System.out.println(response.getBody()); TaskDto processes2 = response2.getBody(); List<TaskDto> t2 = Arrays.asList(processes2); System.out.println("Task Id is " + t2.get(0).getId()); System.out.println("Checker stage id fetched"); // Save the user credentials along with the Pid,tid and tn of the his next task td.setProcessInstanceId(t2.get(0).getProcessInstanceId()); td.setId(t2.get(0).getId()); td.setName(t2.get(0).getName()); custo.setTaskdao(td); customerrepo.save(custo); return "Data inserted successfully";
We are using the latest Camunda v7.12. The BPMN file is attached too.
Why is the process engine getting stuck at the Application stage in some cases?