Subprocess and Process Size Limitations

Hi,

I am currently working on a business process that involves a subprocess executing tasks in parallel. I have a few questions regarding subprocess execution and process size limitations that I was hoping the community could help me with.

  1. What’s the maximum recommended number of subprocess iterations within a single process?
  2. Are there established limitations on process size, such as memory allocation, CPU usage, or other resource constraints?
  3. Any crucial size or limitation impacting project planning?

Thanks in advance!

Regards,
Charumathi

Hi @Charumathi_Kumar - generally speaking, your processes are more constrained by available resources than anything else. Zeebe was designed from scratch to be extremely scalable and efficient. As long as your environment is sized well, you should not run into issues.

To get a better understanding of Zeebe’s capabilities, I think these two pages are great places to start:

Hi @nathan.loding ,

Thank you for your response. Your insights on Zeebe’s scalability and efficiency are indeed useful. I appreciate the recommendation to explore those two pages for a deeper understanding of its capabilities.

I have another query regarding a challenge I’m currently facing in my business process. I’m working with a subprocess that involves executing multiple tasks in parallel. The issue is that all the user tasks created within this subprocess have the same name when displayed in the task list.

Given this scenario, I’m looking for guidance on how to effectively differentiate between these tasks in the task list. Specifically, I’m interested in any recommended practices or features that Camunda provides for customizing task identification or adding labels to tasks.

Any insights or suggestions you could provide would be greatly appreciated.

Regards,
Charumathi

Hi @Charumathi_Kumar - I don’t have a great workaround at the moment, unfortunately. The team is working to add additional context to the Tasklist UI to make it easier to differentiate tasks (here’s the GitHub issue you can subscribe to!). This will be available in a future release, but I don’t have an exact release date yet.

Hi @nathan.loding,

Thank you for your response and for sharing the GitHub issue. I’ve subscribed for future updates. Looking forward to the upcoming release.

Regards,
Charumathi