Issue & Reproduction Steps

1. Create a simple process with a start event, an intermediate task, and an end event.
2. Assign the start event to a group, such as "Requesters" (ensure that the group has only the "View Process Catalog" permission enabled in PROCESS CATALOG), containing at least 13 users, of which 7 are default users (without additional permissions).
3. Have each default user attempt to start a case from the Launchpad.

Current Behavior:

Default users (without additional permissions) may encounter an issue where the "Start This Process" button appears disabled. The problem occurs randomly, so one or more default users will likely face this issue, but not necessarily all of them.

Users with full permissions and administrators can start the process without issues.

This behavior has been replicated across multiple servers with versions 4.11.1 and 4.11.2.

Related Tickets & Packages

https://processmaker.atlassian.net/browse/FOUR-19133

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:deploy