The system log contains a CWWBE0057I message, the process is in
the state "running", but it does not proceed its navigation on the current
path.
Reason
Invoke activities, inline human tasks, and
Java snippets are put in a stopped state, if all of the following happen:
- A fault is raised by the activity
- The fault is not handled on the enclosing scope
- The continueOnError attribute of the activity is set to false
Resolution
The solution to this problem requires
actions at two levels:
- An administrator must repair the stopped activity instance manually. For
example, to force complete or force retry the stopped activity instance.
- The reason for the failure must be investigated. In some cases the failure
is caused by a modeling error that must be corrected in the model.
For example, if you use the WebSphere Scheduler default calendar,
and have an expiration time with 'Timeout' defined for your activity, make
sure that the definition of the time period is in the correct format, in particular
make sure that there is no blank between the number and the unit of time.
Examples of correctly specified timeout periods:
- 1minute
- 2hours 4minutes 1second
- 1day 1hour