FOUR-9412 Fix retry script task

[caleeli]

Issue & Reproduction Steps

During the retry test, a failed script task that was not fixed, changed the process state to ACTIVE when the user pressed "RETRY" instead of remaining in ERROR as intended.

Solution

• Change to ACTIVE only when the script task is completed successfully.

How to Test

• Create a script task with a throw exception
• Add the script to a process
• Run the process
• The task fails, then try RETRY, the request should keep in ERROR status
• Fix the script
• try RETRY again
• The request should continue (to ACTIVE if there is a next task or COMPLETED if it is the last)

Related Tickets & Packages

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

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.

[julceslauhub]

Approved

[julceslauhub]

Approved

[processmaker-sonarqube]

SonarQube Quality Gate

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication