Question
Maantic Inc
US
Last activity: 17 Nov 2023 10:59 EST
Queue processor moving to not running state
Hi,
Queue processor moving to not running state.
In QP dataflow, we see below message.
{"type":".RunStatusTransitionMessage","senderNodeId":"33831ee51ff90137866f8582980d5f64","timestamp":1676524867442,"messageId":"206396bb-0713-4cc2-9d58-d47b6d49bdc8","runId":"pySASBatchIndexClassesProcessor","previousStatus":"PENDING_PICKUP","newStatus":"PENDING_ASSIGNMENT","originator":"CheckAssignmentsTask","reason":"Some assignments were not accepted within given amount of time. Blacklisting [1fb13a62-297f-4bcf-8bb3-45155e4ff849, e054bace-1d63-48cf-a000-0ec7bdcae47e, 1c592e0f-1f74-4c0a-a7a2-f1aca19bb560]"}
***Edited by Moderator Marije to add Capability tags***
Areteans Technology Solutions Pvt. Ltd.
IN
@JohnPaulRaja,C Try to start the QP data flow by using pxStartRunById OOTB activity by passingthe ID of the DDF and also please verify that is there any UTILs node are down or not in state of processing the items in the queue. If you see any node down try to take a restart of UTILs nodes and then monitor.
LTIMindtree
SA
When the QP associated Nodetype is down / moved out of the cluster group, These kind of issues will come. Please check with your Pega Admin on the associated Nodetype even if it's not started after invoking pxStartRunById OOTB activity from the Application.
Evoke Technologies
US
@Kishore Sanagapalli When I invoke pxStartRunById, i can see the error "Could not start the data flow run". What might be the issue? All Associated Nodes r good and running.
LTIMindtree
SA
When the associated nodes moved out of the cluster or went to shutdown state, you'll face that error.