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.
In case of sequencer getting stuck, our cleanup stream can work in several modes - either remove the entire queue or remove only the current (stuck workflow, including the case when you use PROCSEQID). Command:
1176:CUR_eagle_wrf_generic_load:1177:INTRADAY:
unstucks it.