SharePoint 2013 workflow stopped working: what to rebuild in Power Automate

Short answer: SharePoint 2013 workflows are retired in Microsoft 365, so a list that used one will no longer run it. Microsoft's Learn page says they "were turned off for new Microsoft 365 tenants on April 2, 2024, and were fully retired for existing tenants on April 2, 2026." Write down what each old workflow did, then rebuild it as a Power Automate flow.

What Microsoft says happens now

Microsoft's support page "SharePoint 2013 workflow retirement" states:

Existing workflows can only be viewed as raw XML files after SharePoint 2013 workflow is turned off.
There is no option to extend SharePoint 2013 workflow beyond April 2, 2026.

So a workflow that "does nothing" or never leaves a started state is not a bug in your list. The engine is gone. These dates are for Microsoft 365. SharePoint Server on your own servers has its own dates, and I do not cover it here.

Step 1. Find which lists used a workflow

Microsoft's support page names one tool for this: the Microsoft 365 Assessment tool. It says the resulting Power BI Workflow Report shows workflows by site collection and site, recency and volume of usage, lists, libraries and content types that use them, and a Power Automate upgradability score. This tool is meant for admins. If you are not one, send your admin that page.

If you only have a few lists, ask the people who work in them what used to happen on its own: an email, an approval, a status change.

Step 2. Write one line per workflow

For each old workflow, fill in four lines in a plain document:

List or library name.
What started it: an item created, an item changed, or someone starting it on a selected item.
What it did: sent an email, asked for approval, set a field, copied an item.
Who it affected: names or roles.

Microsoft's migration guidance says to inventory "workflow definitions, owners, dependencies, and business processes that still require replacement" before you plan migration.

Step 3. Rebuild each one in Power Automate

Microsoft's Learn guidance gives two example flows: "Send an email when a new item is created in a list" and "Start approval when a new file is added in a library."

Exact names may differ on your screen.

Open the list in SharePoint.
Near the top, select Automate, then Power Automate. Microsoft's page says to then "Select Create a flow to automate a workflow."
Pick a template or start from a blank flow.
Match the trigger to your Step 2 answer. Microsoft's comparison table says Power Automate has triggers for "When an item is created", "When an item is modified" and "When an item is created or modified".
Add the actions. Microsoft lists "Create an item", "Update an item" and "Delete an item", and says to use "Update an item" to set a field value in the current item.
Save and test with one sample item.

For approvals, Microsoft's support page also says: "If basic approval functionality is needed, then the Approvals in Lists & Document Libraries are also a good choice." See "Document approval in SharePoint" and "Power Automate sequential approval".

Loop guard and Sent flag guard

A flow that fires when an item is created or modified and then changes the same item can trigger itself. See "Power Automate flow triggers itself, infinite loop". Our advice, not a Microsoft rule: add a Yes/No column named "Sent", set its default value to No, have the flow check that it is No, send the email or do the action, then set it to Yes. See also "Power Automate email sent multiple times".

Differences Microsoft lists

From Microsoft's Learn comparison:

Flows have a 30 day lifespan. The page says "SharePoint Designer workflows can run endlessly, but flows have a 30 day lifespan." A long wait needs a flow that restarts itself.
Reusable workflows and site workflows are marked "Not available" for Power Automate in that table.
Run history: the page says flows keep a detailed history for runs in the last 28 days, and suggests logging to a list if you need more.
Some workarounds on that page need a Premium license. The page says so, so check your license before you build. See "Power Automate license for a small team".

Move definitions with a tool

Microsoft's Learn page says the SharePoint Migration Tool lets you migrate "SharePoint Designer 2010 & 2013 workflows to Power Automate." Ask your admin whether that fits your case. I have not tested it.

When to get help

You can build all of this yourself in Microsoft 365. If you would rather have it built and tested for your team, I do that. A tracker like this is a fixed price: $5,000 for one, built in 2 weeks. See "What a SharePoint tracker costs to build". Bring one example of the problem to a free call.

Tell me what's still manual

I am Al Davies. I run 250 High Street LLC and build SharePoint trackers and Power Automate flows for operations teams. I work remotely. The first call is free, and I will not try to sell you anything.

See trackers I built: Tools I built

FAQ

Why did my SharePoint 2013 workflow stop working?

Microsoft says SharePoint 2013 workflows were fully retired for existing Microsoft 365 tenants on April 2, 2026.

Can I still see my old SharePoint 2013 workflows?

Microsoft's support page says existing workflows can only be viewed as raw XML files after the workflow is turned off.

What replaces SharePoint 2013 workflows?

Microsoft names Power Automate. For basic approvals it says Approvals in Lists and Document Libraries may fit.

How do I find which lists used a 2013 workflow?

Microsoft names the Microsoft 365 Assessment tool and its Power BI Workflow Report, which an admin runs.

Is there a way to extend SharePoint 2013 workflows?

Microsoft's support page says there is no option to extend them beyond April 2, 2026.