1.6.9 Maximum number of concurrently executable plug-ins in a task
There is a limit on the number of plug-ins in a task that can be executed concurrently in a JP1/AO system. The limit for normal tasks is 100, and the limit for debug tasks is 10. These limits are managed separately. If you execute a plug-in that would cause this limit to be exceeded, the plug-in remains in its state prior to execution until a currently running plug-in has finished.
A plug-in that has been put on hold in this way behaves as follows:
The step enters In Progress status.
The start date and time of the step are set. However, processing of the plug-in does not yet begin.
In the case of a debug task, even if you selected the option that interrupts the flow after each step during debugging, the plug-in will not transition from In Progress to Interrupted status. This is because plug-ins are placed on hold before they can enter Interrupted status.
A message indicating that plug-in execution has started is not output to the task log. This is because plug-ins are placed on hold before the message can be output.
To find out whether plug-ins have been put on hold due to the maximum number of concurrently executable plug-ins being reached, count the number of running plug-ins and compare it against the limit. You can determine how many plug-ins are running by counting them in the task list or debug task list in the Flow area.