5.3.10 Plug-ins that cannot be paused during debugging
Some plug-ins cannot be paused when executing a step, even if Interrupt After Each Step is selected as the break setting for the debug task. When one of these plug-ins is encountered in the debug process, the flow automatically advances to the succeeding step.
|
No. |
Plug-in name |
Can be paused |
|
|---|---|---|---|
|
1 |
Basic plug-ins |
General command plug-in |
Y |
|
2 |
File-forwarding plug-in |
Y |
|
|
3 |
Repeated execution plug-in |
Y |
|
|
4 |
Email notification plug-in |
Y |
|
|
5 |
User-response wait plug-in |
Y |
|
|
6 |
Standard output plug-in |
Y |
|
|
7 |
Terminal connect plug-in |
Y |
|
|
8 |
Terminal command plug-in |
Y |
|
|
9 |
Terminal disconnect plug-in |
Y |
|
|
10 |
Flow plug-in |
N |
|
|
11 |
Interval plug-in |
N |
|
|
12 |
Judge returncode plug-in |
N |
|
|
13 |
Test value plug-in |
Y |
|
|
14 |
Abnormal-end plug-in |
N |
|
|
15 |
Judge value plug-in |
N |
|
|
16 |
Content plug-ins |
Y |
|
|
17 |
Incompatible steps in service templates created in versions of JP1/AO earlier than 10-10 |
N |
|
- Legend:
-
Y: Can be paused. N: Cannot be paused.