If a SharePoint action in an automation rule fails or doesn’t do what you expect, the cause is usually the Microsoft sign-in or the input values. This page explains both and lists the known limitations.
Sign-in and permissions
How it works: SharePoint actions don’t use an app-wide connection. Each action signs in to Microsoft with the account that configured it and uses that account’s delegated permissions.
-
The rule can only reach what this account can access.
-
Microsoft can revoke the sign-in after a password change, MFA reset, revoked session, or long period without use. The actions then fail until someone signs in again in each SharePoint action of the rule.
-
If the account leaves the company or loses access, every rule it signed in to fails.
Keep rules running: Before someone leaves or changes teams, have another person open each SharePoint action in their rules and sign in again.
When you see “Action failed due to invalid input”
This message usually has one of these causes:
|
Likely cause |
What to check |
|---|---|
|
The folder path doesn’t exist in SharePoint. |
Open SharePoint and confirm the exact folder path still exists. |
|
A smart value is empty. |
Check for typos, wrong casing, or a previous action that didn’t run earlier in the rule. |
|
A smart value contains outdated information. Example: The action Get SharePoint item fails when the folder name contains |
Build names and paths from values that don’t change. Example: Name folders with |
Limitations
|
Limit |
What it means |
|---|---|
|
Large files |
Uploads run on Atlassian Forge. Files larger than about 100 MB don’t upload reliably. |
|
Characters in folder names |
SharePoint doesn’t allow |
|
Automation Studio |
The SharePoint actions aren’t available in Automation Studio yet. |