There are several reasons why a process might become stuck in init step, one of them being that 2 (or more) NACs have become associated with a single NES and therefore events sent by the NES are reported to the wrong NAC.
This is caused either by improper network or NES configuration, and will not produce any errors or exceptions, either in the logs or Nolio UI.
To see if this is indeed the issue, please open the
execution.log and locate the following line (it can be located by searching for "getEvents: server"):
2000-01-01 12:00:00,000 ["http-nio-8080"-exec-10] INFO (ExecutionEventsDispatcherImpl.java:47) - getEvents: server [NAC NAME] got [#] requests.
This part of the log shows the number of events dispatched to your NAC ("server [NAC NAME] got [#] requests.").
If more than one NAC is associated with the NES, in the log it will look like so:
2000-01-01 12:00:00,000 ["http-nio-8080"-exec-10] INFO (ExecutionEventsDispatcherImpl.java:47) - getEvents: server [NAC #1] got [#] requests.
2000-01-01 12:00:00,000 ["http-nio-8080"-exec-10] INFO (ExecutionEventsDispatcherImpl.java:47) - getEvents: server [NAC #2] got [#] requests.
Please note that - depending on how the process is built - it is possible that the process may actually work (the actions are executed) and the issue is with the UI not updating accordingly. In other cases the actions might not be executed at all.
Solution
In case this was caused by improper network configuration, what you need to do is isolate the NACs environments using firewall rules.
In case this was caused by a single NES being associated with more than one NAC, (either purposely or by mistake) locate the NAC which is not supposed to be associated with the NES, open Nolio ASAP >> Administration >> Agents Management and delete the NES from this NAC.
As a precaution, it is best to perform both steps in order to ensure no rogue NAC can improperly associate itself with a NES.