Normally, when I complete a user task in TaskList, the form instantly disappear and I have no error message on the Javascript console.
For a given step of my BPMN workflow (a user task), I have a weird behavior: when I complete the task in TaskList, the UI form remains open, after a few seconds, a GET request to /camunda/api/engine/engine/default/task/:id is fired, since the task was closed it gets a 404, at this point a blue banner ‘The task has been removed’ appears at the top (with a ‘Close task’ button).
The request response is: {“type”:“InvalidRequestException”,“message”:“No matching task with id 5a47f25d-26c4-11e8-8bb7-acde48001122”}
This happens most of the time. Sometime (10% of the cases), the form is immedialty closed on completion and I don’t get any error message.
What I don’t understand is why this happens specifically for a certain workflow step. After this step I have two service tasks, which get executed without any problem.
Any hints what is wrong with my setup?
I am using Camunda webapp 7.8.0 running inside tomcat 8.0.47.
Something I tried from the problematic user task followed by two service tasks is to add ‘Asynchronous After’ on it to add an additional save point right after it (and decouple it from the following task). Getting exactly the same though…
I have attached a simplified BPMN process file, which still has the same behavior on the ‘Configuration’ step (form does not get closed, although the two following service tasks are executed sucessfully, then getting ‘The task has been removed’ blue banner + a 404 server request).
everything looks fine and I can complete the user task Configuration without errors. What are you doing in the next service task? Maybe, you get an exception there and the transaction rolls back?
You could set the async after flag for the user task to be sure that the error is not coming from the other tasks.
Do you see any error in the server log file?
Which camunda version are you using?
No, I don’t get any error from the following service tasks (I can see how they start and finish properly). No error in the server logs, except for the 404 call initiated by the Configuration form staying open in the client.
I tried also setting the ‘async after’ on the Configuration user task. But does not solve the problem (which is logical, since the two following service tasks have no issue).
it is working on my side without the start form and I used script task instead of service task. I’m using the same camunda version 7.8.0 (Tomcat 8.0.47).
Weird thing. I downloaded again Camunda 7.8.0 (with Tomcat 8.0.47). And redeployed my two processes from IntelliJ (the standard one and the simplified one you have seen). Fresh db with no old tasks.
I also changed the two following service tasks to script tasks as you did.
But no luck. Still getting exactly the same. The task disappear from the list (middle pane) as soon as I press on complete. But in the right panel, the ‘Configuration’ form remains open + I get a 404 as before. Strange…
How do you deploy your process files? Do you have a spring, web or process application?
Which browser are you using?
Which user are you using for the tasklist login?
we have a similar issue here. Exactly the same versions (camunda 7.8.0 on tomcat 8.0.47).
I also tested with ‘Asynchronous After’ - always the same behaviour.
I also got this with only user tasks in the bpmn, on different browsers (chrome and firefox) and with a ldap server and a postgres attached. I agree with @pajai that in about 10% of the trials it works, in 90% not.
So the question is: when is the task-form closed by the tasklist-app and what could be the reason if it does not.
were you able to solve this issue? I encountered it today and can reproduce it 100%.
The problem occurs if I start a process from the Tasklist and then enter the task form by using the popup notification saying “You are assigned to the following tasks in the same process : link to task”. Completing the task now results in the behavior described by @pajai.
If, on the other hand, I enter the task by using the list in the left panel, the task form is closed after clicking the Complete button and no errors are shown in the console.