Workflow and ServiceDesk Community

 View Only
  • 1.  LBME.WorkflowResponseQueue not processing response files

    Posted Jun 08, 2016 08:51 AM

    Hi Guys,

     

    I have a workflow setup and working that processes an approval e-mail and sends a SendCompleteWorkflowTask message successfully.

    I can see the message in the folder, however it isn't being shown in the queue in System Explorer.

    Workflow.png

    response.png

     

    I have tried to restart the workflow service, restart IIS, rebooted the whole server, removed all the files from the folder.

    I have confirmed the  "Do Not Process Timeouts and Escalations" setting in LocalMachineInfo is NOT checked.

     

    Is there something else I have missed?

     

     

     

     

     



  • 2.  RE: LBME.WorkflowResponseQueue not processing response files

    Posted Jun 08, 2016 10:50 AM

    it may be beneficial to open a support ticket - i've had experiences with this where i've gone round and round trying everything to repair and troubleshoot, and it has turned out (three times now, for me) that there's a bad item in the queue somewhere that symc helps clear out, and it essentially "unclogs" the pipes and the queue starts flowing properly again.  evidently the queue can become completely jammed and stop processing items if there's a corrupt item in the processing queue.

    of course it may be something simple, but it looks like you've covered the simple ones and then some.



  • 3.  RE: LBME.WorkflowResponseQueue not processing response files

    Broadcom Employee
    Posted Jun 08, 2016 04:43 PM

    Unfortunately the LBME.WorkflowResponseQueue isn't problematic at best. We've got a ticket in to try and address the issues with this queue. My recommendation right now is to stay away from anything that requires the use of this queue.



  • 4.  RE: LBME.WorkflowResponseQueue not processing response files

    Posted Jun 09, 2016 10:05 AM

    Thanks TGiles, my colleague raised a ticket yesterday this is probably the one you're referring to.

    We await your response :)