Troubleshooting SharePoint Server workflow validation errors in Visio
Use this reference to resolve validation and error-checking issues in the Microsoft SharePoint Workflow template in Microsoft Visio 2013 and Microsoft SharePoint Designer 2013.
Note
SharePoint 2010 workflows have been retired since August 1, 2020 for new tenants and removed from existing tenants on November 1, 2020. If you’re using SharePoint 2010 workflows, we recommend migrating to Power Automate or other supported solutions. For more info, see SharePoint 2010 workflow retirement.
SharePoint workflow validation issues
The following table lists all of the validation issues that can appear in the Issues pane in Microsoft Visio 2013 or the Visual Designer in Microsoft SharePoint Designer 2013. Each error has a suggested action to take for resolving the problem.
| Error text | Suggested action |
|---|---|
| Duplicate connections exist between workflow shapes. |
Remove the redundant connector by selecting and deleting it. |
| Loop back to parent shape is not allowed within a stage or step. |
Neither Visio Professional 2013 nor SharePoint Designer 2013 supports workflows with implicit loops inside of a stage. Check your workflow for loops and delete the looping connections. If you want to create a SharePoint workflow that includes a set of looping steps inside of a stage, you must use the loop containers. Any actions inside of these containers will loop. Another option is to use stages that go-to a previous stage. |
| Parallel activities that are also sequential are not allowed. |
Activities can be either parallel or sequential, but not both simultaneously. For parallel activities, remove the sequential connectors. For sequential activities, remove the parallel connectors. Sometimes, simultaneously parallel and sequential activities can be difficult to identify. The following validation errors show other common instances of parallel and sequential arrangement and offer alternative arrangements. To avoid having connectors point to the same activity from multiple paths, try duplicating the activity. |
| The condition shape does not have connections labeled with Yes or No. |
Right-click the connector to assign the label "Yes" or "No." |
| The condition shape must have outgoing connections with label Yes and No. |
Ensure that condition shapes have outgoing connectors attached to other workflow shapes. Each condition shape must have a "Yes" and a "No" outgoing connection. |
| The connector is not a SharePoint workflow connector. Use AutoConnect or the connector tool to connect your shapes. |
Avoid reusing connectors from other diagrams as they are not necessarily designed to be used with SharePoint workflows. Delete the selected connector and use the connector tool or AutoConnect to replace with a new connector. |
| The connector must be connected to two workflow shapes. |
Remove dead-end connectors or attach them to a second shape. |
| The diagram must only have one workflow and one Start shape. |
All paths must originate from the same Start shape. Remove extra Start shapes and arrange the connectors so that the path starts in one place. |
| The shape is not a SharePoint workflow shape. Only SharePoint workflow shapes can be connected in a workflow. |
Only workflow shapes from the SharePoint Workflow stencils can be used in the Microsoft SharePoint Workflow template. Other flowchart shapes are not recognized and prevent the workflow from being exported to SharePoint Designer. |
| The Start shape must not have incoming connections. |
Remove the incoming connector to the Start shape. |
| The workflow must have a Start shape. |
Add a Start shape to the beginning of the workflow and connect it to the first activity. |
| The workflow shape is not connected to the workflow. |
If the workflow shape is necessary, add connectors to attach it to the workflow path. Otherwise, delete the shape. |
| Workflow nesting levels must not exceed a maximum of 10. |
Visio 2013 can recognize a maximum of 10 levels of nesting workflow activities. Rearrange the workflow to reduce complexity by eliminating activities or dividing the workflow path into more than one branch. |
| The start shape can only be connected to a workflow stage shape. |
All workflow diagrams must begin with only one Start shape. The Start shape must be connected to a Stage shape. If necessary, add a Start shape to the beginning of the workflow. You can also add a Start shape to the beginning of the workflow in Stage view in Visio 2013. |
| A stage cannot be nested within any other shape. |
Stages are top-level shapes in SharePoint workflow diagrams. You cannot place a shape within any other container shape, including steps, loops, or other stages. If possible, move the stage so that it is outside of all other container shapes and reconnect the stage. If you want to create a logical grouping of actions and conditions within a stage or loop, use a Step shape instead. |
| A stage can only be connected to another stage, condition shape, or a terminator. |
Stages can be connected only to other top-level shapes, including conditions, terminators, or other stages. A stage cannot be connected to actions, steps, or loops at the top level. Rearrange the workflow diagram so that the stage is connected only to other top-level shapes. |
| Stage, step, and loop containers cannot be overlapped. |
The boundaries of container shapes, such as stages, steps, and loops, cannot touch or overlap. If you want to include one container shape within another (for example, include a loop within a stage), be sure that the contained shape is entirely within the bounds of the container. If you do not want one container shape to be contained by the other, space out the shapes in your diagram so that the bounds of the container shapes no longer cross or touch each other. |
| Workflow shapes from other templates/versions are not valid workflow shapes. |
You can use shapes only from the SharePoint Workflow Actions, SharePoint Workflow Conditions, and SharePoint Workflow Terminators stencils, and connectors that are created with AutoConnect or the Connector tool associated with the template in a Microsoft SharePoint Workflow diagram. All other shapes are not valid connections within the workflow validation rules. You can place other shapes on the design canvas as long as they are not connected to the Workflow. If you need to include an action or condition that is not represented with a shape in one of the stencils associated with the Microsoft SharePoint Workflow template, consider creating a custom workflow action. Custom workflow actions can be created in Microsoft Visual Studio 2012 and incorporated into SharePoint workflows in SharePoint Designer 2013. For more information about how to create custom actions in Visual Studio 2012, see the article Develop SharePoint workflows using Visual Studio. |
| A shape cannot be connected outside of the start/end path of the current shape's container. |
All shapes contained within a stage, loop, or step must be entirely contained within that container shape. Shapes cannot connect to any shapes that are not contained in the same container. Rearrange the workflow diagram so that all actions, conditions, loops, and steps within the container shape connect to other shapes in the container. If the shape must connect to an activity outside of the container, connect the shape to the Exit shape associated with the container. |
| Invalid transition shape. |
When a non-condition or non-stage shape is added at the base level of the workflow. Only stages and conditions may exist at the base level of a workflow. Any other shapes that are added to this level will cause this error. You should encapsulate non-condition and non-stage shapes in a condition or stage shape. |
| Stages, steps, and loops may have only one incoming and one outgoing connection. |
All container shapes can have only one incoming connector to the Enter shape that is associated with them. Similarly, container shapes can have only one outgoing connector from their Exit shape. Rearrange the diagram so that each container has a single incoming and outgoing path. You may need to add additional stages or Junction shapes to the workflow to fix this error. |
| A stage name must be unique and cannot be empty. |
Each stage in the workflow must have a unique name. Switch to Stage view and be sure that each stage has its own name. |
| The Project stage has not been configured. |
For Project based workflows, every stage must be linked to a stage on the Project Server. If a stage has not been linked to a stage on the server, you will see this error. To correct this issue, open the Stage property grid and set a stage from the stage drop-down. |
| A parallel activity must begin with a Start Parallel Branch shape. |
Check each parallel activity in the workflow to be sure that it has a Start Parallel Branch shape before the parallel activity begins. |