...
Workflow monitor on the web interface works like the workflow monitor on the desktop Usage Engine desktop where it allows for control of a workflow execution and presents a detailed view of the workflow execution status.
As with monitoring a workflow using desktopUsage Engine desktop, monitoring a workflow on the web interface does not imply exclusive rights to start or stop it, the workflow can be activated and deactivated by another user while monitored, or by scheduling.
| Note | ||
|---|---|---|
| ||
Enabling debug may result in performance degradation when executing the workflow, especially if you have a lot of debug commands in your APL codes. Debug mode is not recommended for the production environment so be sure to disable it after you have done your testing. |
| Note | ||
|---|---|---|
| ||
File sequence |
Viewing Agent Events
While a workflow is running, agents report progress in terms of events. These events can be monitored in the event area at the bottom of the window. The following steps must be taken in order to view these events.
...
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
Viewing Abort Reasons
In most cases if a workflow has aborted, the State will have Aborted displayed next to it. There will be an Error button that you can click to display a dialog containing the abort reason and the stack trace. The System Log also holds valid information for these cases.
...