Call aborted due to WFMaxExecutedStepsExceededException

Revision as of 01:24, 30 January 2010 by Srib (Talk)

Problem Summary	The script could be in an infinite loop and so after 1000 steps are executed, the call is aborted.
Error Message	MIVR-APP_MGR-3-EXCEPTION:com.cisco.wfframework.obj.WFMaxExecutedStepsExceededException: No. of executed steps: 1000
Possible Cause	The script logic is incorrect and so the call got into an infinite loop
Recommended Action	ENG debugs are very essential to troubleshoot these issues. With ENG debugs turned on, you can see the steps executed for a task like 'Execute step of task:' in the logs. Loops will be evident from the ENG debugs. Check the script logic and ensure that there are no infinite loops for the call. Modify the script. 485: Mar 20 09:19:58.968 IST %MIVR-APP_MGR-3-TASK_ABORTED:Application task aborted: Application=App[name=BOI,type=Cisco Script Application,id=0,desc=BOI,enabled=true,max=12,valid=true,optional=[cfgVars=[Lcom.cisco.wfapi.util.WFNameValuePair;@616483,script=BOI-Custom-Prompts.aef,last.modified=1176437737812]],Application Port,id=4,implId=606,active=true,state=IN_USE],aborting=false,transferring=false,disconnecting=false]],Task id=187,000,000,010,Task Class=class com.cisco.app.impl.WFWorkflowAppDebugTaskWrapper,Exception=com.cisco.wfframework.obj.WFMaxExecutedStepsExceededException: No. of executed steps: 1000
Release	Release 7.0(1) Onwards
Associated CDETS #	NA

Rating: 5.0/5 (1 vote cast)