An Advanced Workflow process can only be triggered once per PHP process or HTTP request. This is intended to prevent Sugar Administrators from defining infinitely looping processes. (A real catastrophe!) But what does this mean for PHP customizations?
Assume that you have an Advanced Workflow process enabled for the Contacts module that performs an update on this Contact each time it is saved. If you have an Accounts after_save logic hook that performs an update on each related Contact SugarBean then the process will only run against the first related Contact. Any other related Contact that gets saved during your logic hook execution will not have a process run.
This affects not just logic hooks but any other class of PHP customization such as custom API endpoints or jobs.
If you really need to run that process more than once in the same request, here is a workaround:
use Sugarcrm\Sugarcrm\ProcessManager\Registry; ... Registry\Registry::getInstance()->drop('triggered_starts');
Calling this method will clear the internal Advanced Workflow registry that keeps track of the triggered process starts. After calling this method, the same process can then be triggered again inside the same PHP process or HTTP request.
Careful use of this method can make sure that PHP customizations play nicely with processes defined in Advanced Workflow.