Cchetty: 1 revision

2010-04-09T15:20:54Z

1 revision

← Older revision

Revision as of 15:20, 9 April 2010

Srib: /* Call aborted due to WFMaxExecutedStepsExceededException */

2010-01-30T01:24:55Z

Call aborted due to WFMaxExecutedStepsExceededException

New page

== Call aborted due to WFMaxExecutedStepsExceededException ==

{| border="1"
|-
! '''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'''
| <ol>
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

</ol>

|-
! '''Release'''
| Release 7.0(1) Onwards
|-
! '''Associated CDETS #'''
| NA
|-
|}

[[Category:Unified CCX, Release 8.0]]
[[Category:Unified CCX, Release 7.0]]

Call aborted due to WFMaxExecutedStepsExceededException - Revision history

Cchetty: 1 revision

Srib: /* Call aborted due to WFMaxExecutedStepsExceededException */