feat(FOUR-33043): Define a maxJobs and memory limit for BPMN and default

[pmPaulis]

Issue & Reproduction Steps

Define a maxJobs and memory limit for BPMN and default

Solution

• We defined a new .env variables to define the maxJobs

Current behavior is not possible to define this value and per default is 0 like

PM4_HORIZON_SUPERVISOR_BPMN_MAX_JOBS=0
PM4_HORIZON_SUPERVISOR_1_MAX_JOBS=0 

PM4_HORIZON_SUPERVISOR_BPMN_MAX_JOBS=10
PM4_HORIZON_SUPERVISOR_1_MAX_JOBS=100

How to Test

Describe how to test that this solution works.

Related Tickets & Packages

• https://processmaker.atlassian.net/browse/FOUR-33043

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.

[cursor]

PR Summary

Medium Risk
New default maxJobs values change queue worker lifecycle in all environments unless env is overridden, which can affect throughput and restart timing for BPMN and general queues.

Overview
Adds configurable Horizon worker job limits so BPMN and default queue supervisors can recycle workers after a set number of jobs.

config/horizon.php now sets maxJobs on supervisor-bpmn and supervisor-1 for production, local, and staging, driven by PM4_HORIZON_SUPERVISOR_BPMN_MAX_JOBS (default 10) and PM4_HORIZON_SUPERVISOR_1_MAX_JOBS (default 100). Setting either env var to 0 disables the limit. .env.example documents the new variables.

Unit/integration coverage in HorizonConfigTest asserts defaults, env overrides (including zero), and that queue:work --max-jobs processes a batch of jobs across multiple worker runs.

^{Reviewed by Cursor Bugbot for commit 0f19b1f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[decisions-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[caleeli]

for QA (Alejandro) do some performance tests to make sure this did not impact scripts performance executing at least 30 scripts