Calling Subflow suddenly throws Code 401 "The workflow '' could not be found." Error Code 65

(0) Share

Report

Posted on by SvenThorbergLL

Hello Community,

my workflow (started from PowerApps) worked fine for a few months.

Suddenly a "call subflow" action throws a 401 "The workflow '<id>' could not be found." with error code 65.

Saving a copy of my subflow didn't solve the issue. I also created a new subflow as a test, with this I receive the same error.

Starting my subflow individual works fine.

Any suggestions?

Thank you in advance,

Sven

Categories:

Building flows

I have the same question (0)

All responses (6)

Answers (1)

DO-28032151-0 2 on at

Like (0)

Report

I have the same issue. I turned off the flow and it's not possible to turn on now.

I get this error message, which is nonsense. The original author is logged in.
Flow client error returned with status code "Unauthorized" and details "{"error":{"code":"FlowNotOriginalAuthor","message":"The flow '96a0dacd-acc8-c47e-9b55-a144329fd1fb' is shared. Only the original author can perform management operations on the flow."}}".

Was this reply helpful? Yes No
ronaldwalcott 3,847 Super User 2025 Season 2 on at

Like (1)

Report

Sounds like an authorization issue. Did you say that you removed it from Power Apps the re-added it and it still did not work?

Was this reply helpful? Yes No
SvenThorbergLL 41 on at

Like (0)

Report

@ronaldwalcott thank you for your advice. Unfortunately this doesn't help out.

To try another test I built a completely new flow and added a subflow with noting but a "1" variable, but I also get a "The workflow xyz could not be found" error.

Was this reply helpful? Yes No
SvenThorbergLL 41 on at

Like (0)

Report

meanwhile I found the following: My error throws a "The workflow '9308eac933b4471eb58ce1a3f010d369' could not be found" whereas my subflow has the id 58a1b6bf-a8f3-cb4d-d542-fb8b5bbde224. Is there any possibility that PA is mixing up my flow ids?

Was this reply helpful? Yes No
Ingrid 36 on at

Like (1)

Report

I have the same problem. Last week everything works fine, but today I get the error message when I try to edit the child flow.

The Flow name shown in the message does not exists in the environment.

Request to XRM API failed with error: 'Message: Flow client error returned with status code "Unauthorized" and details "{"error":{"code":"FlowNotOriginalAuthor","message":"The flow '68660d44-2dc8-123e-3eed-c7eefda07fee' is shared. Only the original author can perform management operations on the flow."}}". Code: 0x80060467 InnerError: '.

The flow has only one Owner and was never shared with anyone else.

Was this reply helpful? Yes No
Verified answer

SvenThorbergLL 41 on at

Like (0)

Report

Meanwhile MS Support told me that thay had some Azure Server problems which led to my restrictions.

They have been solved on last Friday so that my flows work well again since then.

Was this reply helpful? Yes No