Hello,
I'm wondering if there is a limit for the maximum workflow elements of a scheduled workflow? I suppose there is some kind of limit and / or bug that is limiting the maximum workflow elements for scheduled workflow because I'm expieriencing the following error why trying to schedule from within a bigger workflow:
1. Create a new workflow with about ~35 single workflow elements (other nested workflows, actions, script elements etc.) and about ~ 8.000 lines of code (looking at the exported workflow xml structure)
2. try to schedule another workflow (lets name it sched_wf) (about 10 workflow elements) FROM this "big" workflow
3. run the "big" workflow --> it will fail while trying to create the scheduled workflow, looking at the log a JPA persistance error is thrown
---> Troubleshooting:
1. Create a new workflow with about ~5 single workflow elements
2. try to shedule the same workflow (sched_wf) as in the initial example FROM this "smaller" workflow
3. run this "smaller" workflow --> it will successfully create a new scheduled task for the workflow we wanted to schedule (sched_wf)
Sooo I guess the java JPA peristance API you're using internaly is reaching some kind of limit, being unable to process the schedule save if the parent workflow that is requesting the sched_wf to be added to the scheduler is to big.
Is there a kown issues for that? Is this is a kown issue: any plans to fix this or any workarounds? What is the limit exacly so I can try to shrink my parent workflow?