Hello,

I'd like to request that Laserfiche consider increasing the service limit for child workflow/business process invocations from the current maximum of 500 per initial instance.

For reference, the current documented limits are:

• 300,000 workflow instances per day

• 25,000 workflow instances per hour

• Maximum of 500 child workflow/business process invocations per initial instance

• Maximum invocation tree depth of 32

The 500-child invocation limit is proving to be a significant constraint for legitimate enterprise automation scenarios.

Our organization frequently performs database queries that identify several hundred to several thousand records requiring the same business process. It is common for us to initiate processing for 300–500+ business processes at once, with each business process consisting of 10–15 workflows. This is a normal operational workload rather than an exceptional case.

Because of the current limit, we have to design our solutions around this restriction. We find ourselves splitting batches, introducing artificial delays, or building additional orchestration logic solely to avoid hitting the limit.

The overall platform throughput limits (300,000 instances/day and 25,000 instances/hour) already provide safeguards against excessive resource consumption. In comparison, the 500-child limit appears disproportionately restrictive, especially for enterprise customers executing bulk operations.

We would like Laserfiche to consider one or more of the following:

• Increasing the default limit substantially (for example, into the tens of thousands).

• Making the limit configurable by administrators.

• Allowing the limit to be adjusted by Laserfiche Support on a per-environment basis.

• Providing guidance on an enterprise-supported pattern for orchestrating large-scale business process execution without requiring custom workarounds.

Our goal is not to generate unusually high workflow volumes, but simply to execute normal enterprise batch operations without having to engineer around this service limit.

We'd appreciate any information regarding whether this limit can currently be adjusted, or whether there are plans to make it configurable in a future release.

Thank you for your consideration.