FOUR-28341: Improve Error Handling for Smart Extract Subprocess

[eiresendez]

Issue & Reproduction Steps

The Smart Extract subprocess surfaced only “Script execution failed with exit code: 1” in the Errors tab, hiding the actual root cause.

Reproduce: run Smart Extract subprocess with an invalid/missing SMART_EXTRACT_API_HOST; the UI shows only the generic exit code and no actionable message.

Solution

• Enhanced error extraction in ProcessMaker/Jobs/ErrorHandling.php to surface concise, meaningful messages from microservice responses (prefers output error/exception/stderr/stdout; trims to first line and limits length; keeps timeout handling intact).
• Added PHPUnit coverage in tests/Unit/ErrorHandlingTest.php for output precedence, stderr first-line trimming, timeout handling and fallback to raw message.

Before:

After:

How to Test

1. Functional UI check: trigger the Smart Extract subprocess with SMART_EXTRACT_API_HOST blank/invalid. In the request Errors tab, you should see the specific message (e.g., “SMART_EXTRACT_API_HOST is required but could not be resolved”) instead of a generic exit code.
2. Unit tests: run php artisan test --filter=ErrorHandlingTest to verify the new error-handling cases.

Related Tickets & Packages

• FOUR-28341

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.

[processmaker-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

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

See analysis details on SonarQube