Others

How to Troubleshoot Azure Logic App SharePoint Trigger Not Running

Emma Brown Oct 13, 2026 868 views

Question details

The user needs to resolve an issue where an Azure Logic App workflow fails to trigger automatically when a new item is created in a SharePoint list.

How to Troubleshoot Azure Logic App SharePoint Trigger Not Running

Product: Azure Logic Apps / SharePoint
Device & OS: not provided
Scenario: Automating workflows or email notifications triggered by the creation of new SharePoint list items.
Observed behavior: The Logic App trigger does not fire, resulting in the workflow missing runs or failing to execute the expected actions.

Before you start

Ensure you have the necessary administrative privileges in your Azure portal to view Logic App run histories, as well as adequate permissions on the target SharePoint site.

Solution 1Recommended

Verify Trigger Configuration and Reauthenticate Connection

Ensure the correct SharePoint trigger is selected and that the API connection is active and authorized.

A common cause for missed Logic App runs is an expired authentication token or a misconfigured target site URL. Refreshing the connection restores the necessary API access.

Open Logic App Designer

Check Trigger Settings

Verify that the primary trigger is explicitly set to 'When an item is created' under the SharePoint connector.

Validate Site Details

Confirm that the 'Site Address' and 'List Name' fields perfectly match the target SharePoint list where items are being added.

Reauthenticate API Connection

Look for any warning icons on the SharePoint connection. Click 'Change connection' or 'Add new' to sign in again with the correct administrator credentials.

Test the Workflow

Save your Logic App changes, manually add a new test item to your SharePoint list, and verify if the workflow triggers successfully.

Verify Trigger Configuration and Reauthenticate Connection

Custom URLs: If your SharePoint site URL does not appear in the dropdown menu, select 'Enter custom value' and paste the full URL manually.

Solution 2

Review Run History and Enable Diagnostic Logs

Analyze the backend logs to pinpoint whether the issue lies in the trigger polling or a failure during workflow execution.

Free Microsoft Office alternative

Looking for a Lightweight Office Suite?

While troubleshooting your cloud automation and SharePoint workflows, you might also need a reliable daily office suite to handle your exported data. WPS Office is a free, lightweight, and fully compatible alternative to Microsoft Office, perfect for managing your spreadsheets, documents, and reports.

1. Download the Installer: Visit the official WPS Office website and download the free installation package for your operating system.
2. Install WPS Office: Run the setup file and follow the straightforward on-screen instructions to complete the installation.
3. Open Your Files: Launch WPS Office and instantly open your existing Office documents or exported SharePoint lists without any formatting issues.

Seamless format compatibility with Microsoft Word, Excel, and PowerPoint (.docx, .xlsx, .pptx).Lightweight installation that opens large datasets exported from SharePoint instantly.Free to use with a familiar, user-friendly tabbed interface for easy migration.

microsoft office alternative - wps office

Frequently Asked Questions

Why does my Logic App trigger history show a 401 Unauthorized error?

A 401 error typically indicates that your SharePoint connection credentials have expired, the password was changed, or the account lacks sufficient list permissions. Reauthenticating the connection in the Logic App designer resolves this.

How long does it take for the SharePoint trigger to fire after an item is created?

The 'When an item is created' trigger operates on a polling interval configured within the trigger settings (e.g., every 3 minutes). It may take up to that specified polling duration for the Logic App to detect the newly created item.

Can I manually force the Logic App to check for new SharePoint items?

Yes. You can manually trigger the workflow by navigating to the Logic App's Overview page and clicking the 'Run Trigger' button. This forces an immediate poll of the SharePoint list.

What should I do if the trigger fires but the email isn't sent?

If the trigger history shows success but the action fails, the issue is likely with the email connector (e.g., Office 365 Outlook) rather than SharePoint. Review the specific run in the 'Runs history' tab to identify which downstream step failed.

Office Quick Solutions