Troubleshooting a workflow that fails mid-workflowIssue <!-- div.margin{ padding: 10px 40px 40px 30px; } table.tocTable{ border: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .6em; padding-bottom: .6em; padding-left: .9em; padding-right: .6em; } table.noteTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:2; } table.internalTable{ border:1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); width: 100%; border-spacing:0; } .sp td{ border-bottom: 1px solid; border-right: 1px solid; border-color:#E0E0E0; background-color: #ffffff; height: 20px; padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; } .sphr td{ border-right: 1px solid; border-bottom: 1px solid; border-color:#E0E0E0; background-color: rgb(245, 245, 245); padding-top: .5em; padding-bottom: .5em; padding-left: .5em; padding-right: .5em; height: 20px; } .title { color: #D1232B; font-weight:; font-size:25px; } .hd1{ color: #D1232B; font-weight:; font-size:18px; } .hd2{ color: #646464; font-weight:bold; font-size:16px; text-decoration: underline; } .hd3{ color: #7a7a7a; font-weight:; font-size:16 px; text-decoration:; } .hd4{ color: #000000; font-weight:bold; font-size:14 px; text-decoration:; } --> This article guides you through the process of troubleshooting a workflow that fails mid-workflow. It provides steps to help you eliminate common causes by verifying that the configuration of your networking is correct. Symptoms may include the following: Workflow is not progressingWorkflow not progressing in domain-separated environmentWorkflow hung on activityWorkflow does not generate a taskWorkflow not foundWorkflow not returningWorkflow does not generate approvalThe generate activity does not create tasks or approvalsDuplicate workflowsDuplicate approvalsSubflow does not returnSubflow running too longSubflow stuckTimer did not executeTimer failedStuck worker with timer stuckStuck work with async wftimer <sysID>Workflow notification not triggeredEvent does not triggerUnable to open workflow ResolutionDetermine whether any of the troubleshooting steps below are true for your environment. Each step provides a link to an article that can help you eliminate possible causes and take corrective action as necessary. Determining if the scheduler is too busy for timers. For more information, see KB0538055: Determine if busy Scheduler is delaying workflow timers. Determine if an approval was manipulated outside of the workflow. For more information, see KB0538242: Determining if an approval was manipulated outside of the workflow. Determine if there are inconsistent domain issues or if the approver is in the wrong domain. For more information, see KB0538502: Determining if there are inconsistent domain issues (approver in the wrong domain).Determine if there was a an exception mid-transaction. For more information, see KB0538284: Determine if there was an exception that prevents workflow from starting or resuming.Determine if there are competing business rules that cause the workflow to stop. For more information, see KB0538069: Determining if there are competing business rules that cause the workflow to stop. Determine if there is a table cleaner issue. For more information, see KB0538279: Determining a table cleaner issue. Note: If the problem still exists after trying the steps in this article, submit an incident to SN Technical Support and note this Knowledge Base article ID (KB0538520) in the problem description. For more information, see Customer Support.