Workflow Soluiton

 View Only
  • 1.  Timeouts and escalations not triggering

    Posted May 12, 2009 01:22 PM

    Hi Everyone,

    I'm having an issue with the timeouts and escalations not triggering. I've set my timeout to 2 minutes as a test and created an escalation for 1 minute that will send a reminder email of a request has not been approved. The thing is it is not triggering either action. I've gone and configured the server according to KB article 43630 regarding this issue but it still won't trigger. Has anyone else experience this issue before as the escalations and time out feature is extremely important for our company.



  • 2.  RE: Timeouts and escalations not triggering
    Best Answer

    Posted May 12, 2009 01:38 PM
    Enable anonymous access to the AutoInvokeDelegateService.asmx and WorkflowManagementService.asmx in the project directory of the published project in IIS.


  • 3.  RE: Timeouts and escalations not triggering

    Posted May 12, 2009 05:39 PM

    Thanks matzebru.

    That worked and i would have never found that out by myself.



  • 4.  RE: Timeouts and escalations not triggering

    Posted May 14, 2009 05:18 PM
    I have two escalataion that is scheduled to run at different times. One is a sends a remnder to approve a request every 2 days. Another escalation is set to trigger at on the 6th day if there has been no approval but this time it is escalated tot he approver's manager. Is there a way to set it so that after the 4th day, it stops sending a reminder to the original approver so that on the 6th day, both don't get sent the email? The first escalation seems to trigger every  2 days but I can't find a way to stop it after it has fired on the 4th day. 


  • 5.  RE: Timeouts and escalations not triggering

    Posted May 14, 2009 07:17 PM
    There are probably several ways to accomplish this, but this should work--use an Add New Data Element towards the beginning of your main model, make it an integer, and set the value to 0 (let's say we call the new variable Counter).  Then in the decision model within first escalation, use the Add Values component to add Counter with the constant value 1.  This will increment your counter each time the escalation is triggered.  Then put in a number range rule to check and see if Counter is less than or greater than something like 3.  So if it's less than 3, it will go down the path of sending the escalation email.  If it's greater than 3, it will not send the escalation email (it will go straight to End).


  • 6.  RE: Timeouts and escalations not triggering

    Posted May 14, 2009 11:51 PM
    Thanks for the suggestion Chris. I wasn't thinking of building a counter but using the date components instead and was having some issues with them.