Hello, it seems LFcloud workflow has a limit of 2500 activities within one instance of a workflow. I am looking up all employees listed under a manager in a lookup table, then running a 'For each row' to create employee folders. When run with many employees it runs into this error, which does not seem to be listed on the LFcloud limitations page. Do I have this correct, each activity is counted.
Question
Question
Workflow instance has been terminated due to exceeding activity invocation limit of 2500 activities
Answer
Demo accounts are limited to 2500 activities per Workflow instance. The error is correct.
Thank you for confirming! Learn something new everyday.
Do you have a list of demo VAR account limitations?
As of right now, subject to change in the future:
- Email attachment size: 2.5GB per month
- Emails: 25000 per month
- Workflow instances: 6000 per hour
- Workflow instances: 25000 per day
- Workflow activities per instance: 2500
- Remote Agents: 1
- Workers per agent pool: 2
- Lookup tables: 10
- Active starting rules: 5
- Conditions per starting rule: 8
- Process* invocation count: 100
- Process* invocation depth: 32
* "process" is a workflow or (forms) business process instance.
Thanks for sharing.
Replies
According to the LF Cloud service limits, that's not the correct number. You are limited in a loop to 500. Within Workflow you are limited to call 10,000 activities in a single instance.
Also, just for clarification, the workflow is creating folders for each manager in the table.
I ran into this same problem even with the 10k limit trying to automatically create folders. I never could find a way around it, since even if I try to ignore folders that have already been taken care of, ignoring a folder counts as an activity too!
Using search criteria to ignore folders works but you will need to invoke workflows which can only create 100 folders at a time.
What is strange to me is that this actually increases the CPU overhead dramatically, because a search is CPU intensive where loops connected to a find entries activity are effectively nothing to a CPU.