In some rare cases (especially related to emergency situations in env) we can see , such as MC crash, MC stopped/restarted, files got stuck) you might find that one or more of launched workflows have “in “In progress” status, however there are no any launched sub-steps (streams). For example:
Note: please do not confuse it with hanging extract-stream. In that case: we are able to expand 
| Info |
|---|
Please note, that this situation differs from a hanging extract stream (in case of hanging extract stream you would be able to expand a workflow line in MT and see that there is |
...
a stream or streams with "Processing" status (not a workflow)) |
...
This page with help you unstuck cleaup the stuck process using built-in EJM instruments and recover Sequencer functionality:
| Table of Contents |
|---|
Reset Sequencer
...
using eagle_ml-2-0_default_cm_sequencer_
...
cleanup
Reset current stuck process (recommended method)
1. Create a .txt file with any name with the following line:
1176:CUR_[workflow_name]:1177:[POSTFIX]:
where:
- CUR_ – is a prefix used when you want to cleanup only current process
...
Reset the entire queue
In case of sequencer getting stuck, we suggest checking estar/tpe/cfg/msgcenter/msgservice.ini config file first of all.
SplitBatchSize parameter should not be a large number, preferred value is 2, in some cases, 1 - it is responsible for memory consumption and values like 100 may harm processing.
...
- (which is stuck),
- [workflow_name] – is workflow name,
- [POSTFIX] – is defined as:
the value of <processingSequencerIdentifier> element of the initial RTR (if this node is not empty and exists). For example, on Sequencer Execution in Parallel Mode page:
Code Block language xml […] <taskIdentifier> <processingSequenceNumber>1</processingSequenceNumber> <processingSequencerIdentifier>PROCSEQID</processingSequencerIdentifier> <correlationId correlationIdScheme="correlationIdScheme">correlationId</correlationId> <businessTaskId correlationIdScheme="businessTaskIdScheme">businessTaskId</businessTaskId> </taskIdentifier> […]The cleanup command should look like this:
Code Block language text 1176:CUR_g_os_eddf_mc_eagle_extract:1177:PROCSEQID:OR the value of the corresponding tag 1177 from related pace event (you can just copy it in Automation Center):
In this case the cleanup command should look as follows:Code Block language text 1176:CUR_g_os_eddf_mc_eagle_extract:1177:MSGCENT:
2. Drop that file to eagle_ml-2-0_default_cm_sequencer_cleanup stream.
3. Wait eagle_ml-2-0_default_cm_sequencer_cleanup stream to complete the cleanup.
4. Done! You can run the process.
Reset the entire queue
| Info |
|---|
Please note, that this way you will cleanup not only the current stuck process, but the rest of the queue as well |
You should form a message as above, but with ALL_ prefix.
1176:ALL_[workflow_name]:1177:[POSTFIX]:
Example:
| Code Block | ||
|---|---|---|
| ||
1176:CUR_eagle_ALL_g_os_eddf_mc_eagle_extract:1177:PROCSEQID: |
Reset Sequencer using eagle_ml-2-0_default_cm_nuggetizer_recover
| Info |
|---|
Using Nuggetizer is quite similar to unstucking a single process with Sequencer cleanup, but you do not need to form any messages, everything is done via panel |
...
- Go to the Message Center Console/Editor.
- Find eagle_ml-2-0_default_cm_nuggetizer_recover stream and right click on it
- Choose Run Now With Overrides:
- In the opened Run Now With Overrides window, right click somewhere in the List Options, press Debug
- And tick Show Hidden Cells:
- Add the following parameters: Mode = Recovery, Option = All Queue and Workflow Name = eagle_wrf_generic_load:
...
- Press Ok
The sequencer was now reset in the region.