In some situations, the system may include many tasks in a single database transaction. However, if the number of tasks being created at time is very high (e.g., all pages in a ~20,000 page submission being sent to Classification at once), delays in processing may occur.
In v41.0.1 and later, you can use the HYPERFLOW_ENGINE_MAX_TASKS_PER_DB_TRANSACTION ".env" file variable to specify the maximum number of workflow-engine tasks that are included in a single database transaction:
HYPERFLOW_ENGINE_MAX_TASKS_PER_DB_TRANSACTION=<maximum_number_of_tasks>By default, no more than 30 tasks are included in a database transaction. If you're noticing delays in submission processing, particularly if you are processing submissions with thousands of pages, our Support team may recommend decreasing the value of this variable.