OneDrive "When a file is created" trigger suddenly stopped working

(0) Share

Report

Posted on by CU24080233-3

Hello everyone,

I have been using a Power Automate flow with the OneDrive for Business - "When a file is created" trigger for several months without any issues. The flow was working normally until around the end of July.

However, recently the trigger suddenly stopped working and now shows the following error: Internal server error occurred while invoking API.

The OneDrive connection is healthy.

Re-authenticated the connection.

Duplicated the flow and recreated the trigger.

Existing successful runs can still be manually re-run without issues.

Other OneDrive actions (Create file, Get file content, etc.) continue to work normally.

Categories:

Using connectors

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

11manish 4,376 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Your troubleshooting already strongly indicates that this is not a bad OneDrive connection or a problem with the downstream flow.

The critical clue is that OneDrive actions continue to work while the event trigger fails with an internal API error. The OneDrive for Business connector currently

supports both When a file is created (OnNewFileV2) and When a file is created (properties only) (OnNewFilesV2).

Therefore, my first production-safe workaround would be:

Replace When a file is created with When a file is created (properties only) → Get file content → continue with the existing processing.

If both triggers fail, I would stop modifying the flow and escalate it as a likely OneDrive for Business connector trigger/service issue, providing Microsoft with the

exact error and request/correlation ID.

And importantly, don't delete the original production flow yet. Keep it intact while you run the isolated trigger tests; that gives you a much better diagnostic

baseline.

Refer:

https://learn.microsoft.com/bs-latn-ba/connectors/onedriveforbusiness

Was this reply helpful? Yes No
Suggested answer

Haque 4,086 Super User 2026 Season 2 on at

Like
a
(0)

Report
Copy link

Link copied!

Hi @CU24080233-3,

The error is a known intermittent issue often related to backend service or connector problems rather than your flow configuration - if you please can check MS 365 service health for any ongoing incidents.

In this case I would do some quick check first, these are as follows:

1. Re-authenticate the connection of the triggers.

2. Fix the folder id - I assume if you typed or pasted a folder path and if it doesn't match - the trigger may fail (any recent change?)

3. A change of location sometimes help to troubleshoot - please do a test on Root vs Subfolder. Please try to set the folder path to root (/) to check if the trigger fires correctly. Subfolders can sometimes drop connections if permissions or shared folder links change.

And of course 11manish has mentioned the good alternatives.

I need to know one answer from you - does the flow fail on saving/registering the trigger or during a an actual file uplaod?

I am sure some clues I tried to give. If these clues help to resolve the issue brought you by here, please don't forget to check the box Does this answer your question? At the same time, I am pretty sure you have liked the response!

Was this reply helpful? Yes No