Al darle submit en un formulario me esta dando el error:
Error : { “exception”: “class org.bonitasoft.engine.bpm.flownode.UserTaskNotFoundException”, “message”: “USERNAME=pbonillo | Activity instance with id 7714204669445061423 not found” }
Lo que tengo es un proceso que inicia con un formulario y termina. (El usuario es pbonillo porque tengo una organización creada por mi).
Ayuda no se como resolver esto. Si se necesita más especificaciones las dare
For as much as I understood, I am experiencing the same issue.
I reckon this happened after I renamed the users of my organization. I think what happened is that there was an unfinished task for a particular username that was not complete, which caused a problem once the user was deleted/renamed. I tried to login with another user of the same type but the task is not listed (probably because it was already assigned to the first user). Furthermore, when I try to run the process I’m always prompt to the same form that causes the error, so I’m stuck there. Is there a way to visualize all the activity instances still active and delete them?
Thanks in advance.
Best
Hello,
After experiencing the same issue, I managed to get rid off this error by regenerating an instantiation form for my Pool.
The error might come from a form you're using on a task and for instantiating your datas. In my case, I was using the same form for both instantiation and for the next task and the same error popped up (I'm on Community 7.14).
While I can't tell you the source of this error, I hope that my answer helps you go around it.
Best regards,
How your task is assigned to the user? Is it using an actor and actor mapping or using an actor filter?
Do you have step by step instruction to reproduce the issue? If yes you might want to open a bug on the issues tracker.
The task is assigned using actor mapping without a filter. Another strange thing is that the username reported in the exception is not the actor that should perform that task (which is associated with another actor).
I do not remember all the steps that brought me to this deadlock. I will test and in case I can reproduce it I will open a bug report. Meanwhile, what will be the best way to overcome this situation? I thought to create a copy of the original diagram from scratch and rename at least the troublesome task and the diagram name.
Thanks in advance.
Best
What you can do is to take a look at the content of flownode_instance table in the Engine database and double check that you don’t have any task with id = 7714204669445061423.
Then you can take a look at arch_flownode_instance and check if you have an entry where sourceObjectId = 7714204669445061423.
It can help to figure out if the task was actually performed or is maybe in failed state…