Power Platform Community Forum Thread Details

[Title]

PAD 2.57 / Default environment / “Create a copy” fails with Entity 'workflow' Does Not Exist (0x80040217)

(repro on brand-new simple flows; portal duplicate doesn't show up)

[Product]

Power Automate for desktop (PAD) / Desktop flows

[When did it start?]

Since mid-Jan 2026 (it used to work before)

[Environment / Account]

- Sign-in: Work account

- Environment: Only Default is available (no other environments shown)

- PAD version: 2.57

[Summary]

In PAD, “Create a copy” fails for ALL desktop flows (including a newly created simple flow).

Error: Entity 'workflow' Does Not Exist (0x80040217).

Additional note:

If I duplicate the desktop flow from the Power Automate portal, it shows no error,

but the duplicated flow never appears in the list afterwards (so duplication is not usable).

[Steps to reproduce (PAD)]

1. Open PAD and sign in with a work account

2. Go to Desktop flows list

3. Pick any flow (even a brand-new simple flow)

4. Click “Create a copy”

5. Observe the error below

[Expected]

- A duplicated flow is created in the same environment and is visible in the list

[Actual]

- PAD duplication fails with Entity 'workflow' Does Not Exist (0x80040217)

- Portal duplication shows no error but the duplicated flow never appears

[Error details (IDs fully masked for safety)]

Correlation ID: [masked]

Exception message: Entity 'workflow' With Id = [masked] Does Not Exist

HTTP status: NotFound

Error code: 0x80040217

HResult: -2146233088

ResponseContent: {"error":{"code":"0x80040217","message":"Entity 'workflow' With Id = [masked] Does Not Exist"}}

RequestId: (blank)

REQ_ID: [masked]

x-ms-service-request-id: [masked]

If needed, I can share the full IDs privately with Microsoft moderators/support only.

[What I tried]

- Repro on brand-new simple flows (not specific to one flow)

- Refresh / sign out / sign in: no change

- Portal duplicate: no visible error, but duplicated flow never appears

[Questions]

1) Is anyone else seeing this issue recently? (please share timing and PAD version)

2) Is this a known regression/service issue?

3) Any workaround (alternative copy method, cache reset, etc.)?

4) What logs/diagnostics can an end user collect for this scenario?

Categories:

Power Automate Desktop

Hello There,

This error is tied to a change in how desktop flows are stored in Dataverse. In Power Automate for Desktop (PAD), “Create a copy” relies on the workflow entity in Dataverse. Since mid‑January 2026, Microsoft seems to have adjusted the schema, and PAD is now throwing Entity 'workflow' Does Not Exist (0x80040217) when trying to duplicate flows in the Default environment.

Check release notes: Microsoft often fixes PAD regressions in the next patch. Keep an eye on the Power Automate release notes for PAD updates.

This is a known regression in PAD 2.57 affecting the Default environment. The safest workaround is to export/import flows manually until Microsoft issues a fix.

✨ If my response helped resolve your issue, please mark it as ✅ Accepted Answer and give it a ❤️ like — it helps others in the community find solutions fasterommunity find solutions faster. Thank you!