Issue & Reproduction Steps

Populate cases_started table - DB Exception when populating the cases_started table
The User starts a process that has been assigned.

• The cases_started table cannot be populated because of a DB error like a blocked table.
• The system catches the problem and does not register the record so the cases_started got incomplete. Rollback transaction.
• Later the CloudOps user can run a command to resync the cases_started table.

Resync command:

php artisan cases:sync –-request_ids=1,2,3

Related Tickets & Packages

FOUR-18602

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.

ci:next