I'm encountering an intermittent issue when using a!startProcessLink within a a!richTextItem in a task. The process model being called is fully chained from Start to End and works fine when called from a Record as a Record Action. But in this case where I am calling from a Task, once the process ends, I sometimes get the error message: "The Task Could Not Be Submitted. The task has already been submitted." This occurs sporadically. Any insights into why this might be happening and how it can be resolved?
Thank you!
Discussion posts and replies are publicly visible
senthilarumugamr said:But in this case where I am calling from a Task
I am not sure if I understood this. What do you mean?
Hi senthilarumugamr ,
If you are viewing interface via user input task and it has any exception flow, then the message "The Task Could Not Be Submitted. The task has already been submitted" will be visible when exception flow executed. Thats the reason it occurs sporadically. If above is the scenario, then please check the time required for exception flow. This might help
Looks like the initial task from where you launched the startProcessLink has been completed (either by another user or perhaps by the process initiated by the startProcessLink).
Hard to resolve without knowing a little more about how this is designed.
There is no exception flow configured - neither on the parent task nor within the process triggered via the a!startProcessLink.
The original task itself is accessible only to the current user, and that user is redirected to the new task within the process called from startProcessLink.
When user hits submit in the child process's task, the child process flows into End node and the user gets redirected back to the original task. This is working fine say, 8 out of 10 times. But occasionally the 'Task cannot be submitted as it is already completed' error appears. Even when this error is thrown, the task is not really completed and it is available in My Tasks for user to pickup and complete. So, the issue really is the annoying incorrect error message appearing out of seemingly nowhere and breaking the UX flow.
What is the reason to call a process from a task in a process?