Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In some rare cases (especially related to emergency situations in env, such as MC crash, MC stopped/restarted, files got stuck) you might find that one or more of launched workflows have “In progress” status, however there are no launched sub-steps (streams). For example:

...

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 processresume Sequencer, it will continue processing the queue with the next sequence number

Info

The stuck record was not loaded to DB, so we recommend loading this record manually (w/o Sequencer) to keep data integrity.

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

...

  1. Go to the Message Center Console/Editor.
  2. Find eagle_ml-2-0_default_cm_nuggetizer_recover stream and right click on it
  3. Choose Run Now With Overrides:

  4. In the opened Run Now With Overrides window, right click somewhere in the List Options, press Debug

  5. And tick Show Hidden Cells:


  6. Add the following parameters: Mode = Recovery, Option = All Queue and Workflow Name = eagle_wrf_generic_load:


  7. Press Ok

The sequencer was now reset in the regionwill be unstuck and will continue processing the queue with the next sequence number.


Info

The stuck record was not loaded to DB, so we recommend loading this record manually (w/o Sequencer) to keep data integrity.