Process return to home page when data is to big, but no error found in process instance

My company has a huge process model, includes hundreds of nodes and a lot sub process, there are a lot form nodes in this pm, they all having activity chaining and assigned to same user, we are developing on this pm and also have changes on ui and forms.

When user finish and submit this form, will automatically redirect to next form node and do next form.

Form data is complex list of cdt saves in process variables, and will write to db

The problem is, our form can add multiple blocks of a same form, this can make list of data very big, when we added too many form blocks, likely 30 + blocks, then submit, then it shows a little action complete banner, and redirects to home page, but you can countiune this process and find next task in current user’s tasks, user can countiune task with no error. And in process instance monitoring, no error.  I guess it’s data size problem, but I didn’t find a way to resolve this problem, some times there will be a huge form.

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Lead Developer

    As per my understanding there are no errors but activity chaining is failing after a certain user input task node (i guess this is what you mean by 'blocks') and the next form is not shown after the previous one. 

    If this is the case, then I strongly recommend optimising the process and form designs - like using multiple related actions instead of one big action for the user is better in cases like these. Huge processes with synchronous/activity chained node activities limit performance in many ways. 

Reply
  • 0
    Certified Lead Developer

    As per my understanding there are no errors but activity chaining is failing after a certain user input task node (i guess this is what you mean by 'blocks') and the next form is not shown after the previous one. 

    If this is the case, then I strongly recommend optimising the process and form designs - like using multiple related actions instead of one big action for the user is better in cases like these. Huge processes with synchronous/activity chained node activities limit performance in many ways. 

Children
No Data