OneDrive for Business "Copy File" Unauthorized Error

(4) Share

Report

Posted on by JK_80

Hi,

I encountered a strange behaviour / bug in the "Copy File" Action in my Cloud flows.

I have a flow with a trigger "When a file is modified (properties only)":

File is opened with "Get file content".
Content is checked.
If this check is true, the file is copied to another place with "Copy File".

The "Copy File" returns an 401 error

{
 "status": 401,
 "message": "Unauthorized",
 "source": "api.connectorp.svc.ms"
}

But if I look in the OneDrive for Business Folder, the files is copied correcty.

I also implemented a delay of 30 seconds before copying the file and created a new Manual Cloud Flow which has only the "File Copy"-Action. Same problem there.

The Flow is triggered at least once a month and at beginning of April, the flow was executed correctly.

Does somebody has encountered an similar problem? For me, it looks like the action is returning a wrong status code, despite working correctly.

Any ideas or feedback would be great.

Categories:

Using connectors

All responses (8)

Answers (0)

Sort by

8BitWarrior 68 on at

Like
a
(2)

Report
Copy link

Link copied!

I am also experiencing the above issue (since May 2nd) with workflows that have been running without issue for years. Now all of a sudden the OneDrive for Business Copy file steps are failing with an Unauthorized error.

Hoping to get a resolution to this issue soon.
CU24100807-0 11 on at

Like
a
(2)

Report
Copy link

Link copied!

I am in the same situation. Copy file with OneDrive for Business is failing in all the flows
It has no sense. They were working correctly before
Lundsteen on at

Like
a
(1)

Report
Copy link

Link copied!

Happen to me too.
asthalon628 2 on at

Like
a
(0)

Report
Copy link

Link copied!

I encountered the same issue. There's an open service advisory right now for issues with Convert File (OD789650) and I have to wonder if it isn't related.

At any rate, I implemented a workaround in my affected flow by following the Copy Activity on failure with a Get File Metadata Using Path action against the destination path of the Copy, to validate the presence of the file. If you're actually overwriting you need to do a bit more work validating attributes, but if the Copy is a new file then presence is ideally good enough.
CU24100807-0 11 on at

Like
a
(0)

Report
Copy link

Link copied!

Certainly, I've just implemented this and it has worked.

All the same, this morning my flow was working correctly without having made any changes. Sometimes I can't understand these mysteries....
JK_80 14 on at

Like
a
(1)

Report
Copy link

Link copied!

@mcrislg wrote:
Certainly, I've just implemented this and it has worked.

All the same, this morning my flow was working correctly without having made any changes. Sometimes I can't understand these mysteries....
Didn't make any changes yet, but flow has still errors. But it could be that they are implementing a fix, which is not available in all datacenter regions yet.

I'll keep an eye on issue MO791038, which replaces OD789650 to see if anything works again, if this issue is resolved. If not the issue has to be reported somehow, because who knows, what else is affected.
HenryPF 30 on at

Like
a
(0)

Report
Copy link

Link copied!

We are experiencing the same issue. A flow that's worked perfectly for months and which we haven't touched, is now giving us "Unauthorized" errors at the Copy File action.
JK_80 14 on at

Like
a
(0)

Report
Copy link

Link copied!

Connector seems to work again as expected. Today I got no error.