Merge pull request #10250 from jansenbe/bjansen/workflowretirementnotice

Cloud-Writer · web-flow · commit 36052b98a879 · 2025-12-02T16:08:09.000-08:00
AB#8446: Make it very clear workflow 2013 is retired and will stop working on …
diff --git a/SharePoint/SharePointOnline/workflows/configured-workflow-fails-running.md b/SharePoint/SharePointOnline/workflows/configured-workflow-fails-running.md
@@ -13,11 +13,14 @@ ms.custom:
   - CSSTroubleshoot
 appliesto: 
   - SharePoint Online
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # "Daily email limit has exceeded and your workflow has been suspended" or "Unable to send to a recipient" error in a SharePoint Online workflow
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Problem
 
 Consider the following scenario:
diff --git a/SharePoint/SharePointOnline/workflows/connecting-site-workflow-problems.md b/SharePoint/SharePointOnline/workflows/connecting-site-workflow-problems.md
@@ -14,11 +14,14 @@ ms.custom:
 appliesto: 
   - SharePoint Online
   - SharePoint Server 2013
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # Workflow problems after you connect to a SharePoint Online or SharePoint Server 2013 site
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Problem
 
 Consider the following scenario.
diff --git a/SharePoint/SharePointOnline/workflows/copied-workflow-linked-to-source-workflow.md b/SharePoint/SharePointOnline/workflows/copied-workflow-linked-to-source-workflow.md
@@ -13,11 +13,14 @@ ms.custom:
 ms.author: meerak
 appliesto: 
   - SharePoint Online
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # A SharePoint Online workflow that was copied and pasted from a Workflows Site Object in SharePoint Designer is linked to the source workflow
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Problem
 
 Consider the following scenario:
diff --git a/SharePoint/SharePointOnline/workflows/error-reported-in-sharepoint-2010-workflow-status.md b/SharePoint/SharePointOnline/workflows/error-reported-in-sharepoint-2010-workflow-status.md
@@ -13,11 +13,14 @@ ms.custom:
   - CSSTroubleshoot
 appliesto: 
   - SharePoint Designer 2013
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # A Workflow Status error is reported when a SharePoint 2010 workflow stops
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Symptoms
 
 As you create a Microsoft SharePoint 2010 workflow in Microsoft SharePoint Designer 2013, one of the available workflow actions is **Stop Workflow**. The **Stop Workflow** action sets the status of the workflow instance to **Completed** and optionally logs a custom message to the **Workflow History** list.
diff --git a/SharePoint/SharePointOnline/workflows/gather-workflow-data.md b/SharePoint/SharePointOnline/workflows/gather-workflow-data.md
@@ -15,11 +15,14 @@ ms.custom:
 ms.author: meerak
 appliesto: 
   - SharePoint Online
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # Gather SharePoint 2013 Workflow troubleshooting data with ShowScopeDebugInfo
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 The **ShowScopeDebugInfo()** function provides an easier way to troubleshoot common problems that affect SharePoint 2013 Workflows, and also provide additional information to Support agents who help you to resolve Workflow problems.
 
 ## How to run the ShowScopeDebugInfo() function
diff --git a/SharePoint/SharePointOnline/workflows/item-pending-status.md b/SharePoint/SharePointOnline/workflows/item-pending-status.md
@@ -13,11 +13,14 @@ ms.custom:
   - CSSTroubleshoot
 appliesto: 
   - SharePoint Online
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # SharePoint Online item that requires content approval reverts to "Pending" status
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Problem
 
 Consider the following scenario:
diff --git a/SharePoint/SharePointOnline/workflows/nintex-workflow-fails-to-start.md b/SharePoint/SharePointOnline/workflows/nintex-workflow-fails-to-start.md
@@ -15,11 +15,14 @@ ms.custom:
   - CI 146979
 appliesto: 
   - SharePoint Online
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # Nintex workflow on SharePoint Online doesn't start
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Symptoms
 
 When you try to run the Nintex workflow on SharePoint Online, you receive the following error message:
diff --git a/SharePoint/SharePointOnline/workflows/publishing-approval-workflow-fails-starting.md b/SharePoint/SharePointOnline/workflows/publishing-approval-workflow-fails-starting.md
@@ -14,11 +14,14 @@ ms.custom:
 appliesto: 
   - SharePoint Online
   - SharePoint Server
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # Publishing Approval workflow doesn't automatically start in SharePoint Online or in SharePoint Server on-premises
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Problem
 
 A Publishing Approval workflow that uses the Microsoft SharePoint 2010 Workflow platform doesn't start automatically in SharePoint Online or in an on-premises installation of SharePoint Server. On the Workflow Status page, you receive the following error message:
diff --git a/SharePoint/SharePointOnline/workflows/reload-the-page.md b/SharePoint/SharePointOnline/workflows/reload-the-page.md
@@ -15,11 +15,14 @@ ms.custom:
 ms.author: meerak
 appliesto: 
   - SharePoint Online
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # SharePoint 2013 Workflow Error: "To try again, reload the page and then start the workflow"
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Symptoms
 
 When starting a SharePoint 2013 Workflow, you encounter the following error message displayed in an alert:
@@ -38,7 +41,7 @@ This error occurs if SharePoint 2013 Workflows are in a suspended state for the
 
 You can remove the current SharePoint site's suspension by removing SharePoint 2013 Workflows that have exceeded their limits. Use the Workflow Settings page, or delete workflows using SharePoint Designer.
 
-The cleanup process isn't instant. It takes time and the Workflow Health switches to a **Connected** status when it's done:
+The cleanup process isn't instant. It takes time and the Workflow Health switches to a **Connected** status when it is done:
 
 :::image type="content" source="./media/reload-the-page/workflow-connected.png" alt-text="Screenshot of the Workflow Health page showing workflow status as connected.":::
 
@@ -48,7 +51,7 @@ You can identify the workflows to be removed by using the **ShowScopeDebugInfo()
 
 ### How to run the ShowScopeDebugInfo() Function
 
-1. On the site that is having the Workflow problem, select Settings (the gear icon), and then select **Site Settings** > **Workflow Settings** > **Workflow Health**.
+1. On the site that's having the Workflow problem, select Settings (the gear icon), and then select **Site Settings** > **Workflow Settings** > **Workflow Health**.
     - You can also access Workflow Health from a URL. Example URL: `https://contoso.sharepoint.com/sites/test/_layouts/15/WorkflowServiceHealth.aspx` - in this example, replace *contoso* with your domain, and *test* with the name of the SharePoint site.
 1. Open the Developer tools from the browser (Microsoft Edge or Google Chrome is recommended).
     - For Microsoft Edge, press the F12 key to toggle open Developer Tools.
@@ -103,6 +106,6 @@ You can identify the workflows to be removed by using the **ShowScopeDebugInfo()
 
     **Workflows are suspended**
 
-1. Once a Workflow or Workflows are removed, a cleanup process is started. You can track the progress by refreshing the Workflow Service Health page and executing the ShowScopeDebugInfo function. **ActiveMessageCount**, **ScopeSizeInBytes**, and **CorrelationFilterCount** will go down, depending on which limit was exceeded.  **ActiveMessageCount** is the slowest and might take days to clear up, but it isn’t blocking. Once the core of the cleanup background job is done, the Workflow Service Health page will no longer display **Workflows are suspended**, and the **StatusDetails** will no longer have a value.
+1. Once a Workflow or Workflows are removed, a cleanup process is started. You can track the progress by refreshing the Workflow Service Health page and executing the ShowScopeDebugInfo function. **ActiveMessageCount**, **ScopeSizeInBytes**, and **CorrelationFilterCount** will go down, depending on which limit was exceeded. **ActiveMessageCount** is the slowest and might take days to clear up, but it isn’t blocking. Once the core of the cleanup background job is done, the Workflow Service Health page will no longer display **Workflows are suspended**, and the **StatusDetails** will no longer have a value.
 
 If you can't fix the issue by removing workflows, you might opt to open a support request. If you choose to open a support request, gather some additional information about the workflow health by using the **ShowScopeDebugInfo()** function. For more information about the **ShowScopeDebugInfo()** function, see [Gather SharePoint 2013 Workflow troubleshooting data with ShowScopeDebugInfo](./gather-workflow-data.md).
diff --git a/SharePoint/SharePointOnline/workflows/replace-list-item-permission-fail.md b/SharePoint/SharePointOnline/workflows/replace-list-item-permission-fail.md
@@ -14,11 +14,14 @@ ms.custom:
 appliesto: 
   - SharePoint Online
   - SharePoint Server
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # SharePoint workflow that uses the "Replace List Item Permissions" action fails
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Problem
 
 Consider the following scenario:
diff --git a/SharePoint/SharePointOnline/workflows/workflow-contains-blank-values.md b/SharePoint/SharePointOnline/workflows/workflow-contains-blank-values.md
@@ -14,11 +14,14 @@ ms.custom:
 appliesto: 
   - SharePoint Online
   - SharePoint Server
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # Workflow that uses the SharePoint 2013 Workflow Platform Type contains blank values in output from the "Multiple lines of text" column
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Problem
 
 Consider the following scenario:
diff --git a/SharePoint/SharePointOnline/workflows/workflow-http-unauthorized.md b/SharePoint/SharePointOnline/workflows/workflow-http-unauthorized.md
@@ -13,11 +13,14 @@ ms.custom:
   - CSSTroubleshoot
 appliesto: 
   - SharePoint Online
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # "SharePoint 2013 workflow HTTP Unauthorized" error occurs
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Problem
 
 When you try to run a Microsoft SharePoint 2013 workflow in Microsoft SharePoint Online, you receive an error message that resembles the following example:
diff --git a/SharePoint/SharePointOnline/workflows/workflow-lookup-fails-executing.md b/SharePoint/SharePointOnline/workflows/workflow-lookup-fails-executing.md
@@ -14,11 +14,14 @@ ms.custom:
 appliesto: 
   - SharePoint Online
   - SharePoint Server 2013
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # A SharePoint workflow that uses a site column to perform a lookup on a list on a different site doesn't execute
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Problem
 
 Consider the following scenario:
diff --git a/SharePoint/SharePointOnline/workflows/workflow-update-list-item-fail.md b/SharePoint/SharePointOnline/workflows/workflow-update-list-item-fail.md
@@ -13,11 +13,14 @@ ms.custom:
   - CSSTroubleshoot
 appliesto: 
   - SharePoint Online
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # SharePoint Online workflow that uses the Update List Item action fails to update a Person or Group column
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Problem
 
 Consider the following scenario:
diff --git a/SharePoint/SharePointOnline/workflows/workflow-using-impersonation-step-fails-completed.md b/SharePoint/SharePointOnline/workflows/workflow-using-impersonation-step-fails-completed.md
@@ -1,6 +1,6 @@
 ---
 title: SharePoint workflow using an impersonation step doesn't complete
-description: SharePoint workflow with an impersonation step that you return field values for a user account as something other than As a string does not finish when you run it.
+description: SharePoint workflow with an impersonation step that you return field values for a user account as something other than a string doesn't finish when run.
 author: Cloud-Writer
 manager: dcscontentpm
 search.appverid: 
@@ -15,11 +15,14 @@ appliesto:
   - SharePoint Online
   - SharePoint Server 2013
   - SharePoint Server 2010
-ms.date: 12/17/2023
+ms.date: 12/02/2025
 ---
 
 # A SharePoint workflow that uses an impersonation step doesn't complete when you return field values for a user account as something other than "As a string"
 
+> [!IMPORTANT]
+> SharePoint 2013 workflow has been turned off on all newly created tenants since April 2, 2024. It will be removed from all existing tenants on April 2, 2026. See [SharePoint 2013 workflow retirement](https://support.microsoft.com/office/sharepoint-2013-workflow-retirement-4613d9cf-69aa-40f7-b6bf-6e7831c9691e) for more information.
+
 ## Problem
 
 Consider the following scenario:
@@ -30,9 +33,9 @@ Consider the following scenario:
   - Return a field that has a value other than **As a string**.
   - Use the value in that field to change permissions.
 
-- The field that you are trying to collect information from contains user accounts.
+- The field that you're trying to collect information from contains user accounts.
 
-In this scenario, when you run the workflow, the workflow does not finish, and the status is displayed as **Error Occurred**.
+In this scenario, when you run the workflow, the workflow doesn't finish, and the status is displayed as **Error Occurred**.
 
 ## Solution
 
