Fix Power Automate Email Loop
Budget: ₹600 – ₹1,500 INR
I built a cloud flow in Power Automate that triggers every time a file is added to a SharePoint document library and then emails me the uploader’s name and the file name. The SharePoint side must remain untouched, yet two problems have surfaced during testing:
• the flow falls into an endless email loop, and
• when different users upload different files, each message lists every file as though every uploader added it.
All I really need is for the flow to fire once per upload, name the correct uploader, and then stop—no recycling, no cross-reporting. The incoming mail can stay one-email-per-file; I just want the looping behaviour gone.
You’ll receive a copy of the current flow (triggered by “When a file is created” and using standard Office 365 Outlook actions). Please identify the exact cause of the recursion, apply the fix—whether that means adding trigger conditions, concurrency controls, Do Until exits, unique IDs, or any other best-practice safeguard—and return a working version that I can import straight back into my tenant. A short note explaining the change set will help me support it later.
When you send your proposal, walk me through the approach you’d take and the specific adjustments you expect to make in the designer; the clearer your plan, the faster I can select and grant access.
• the flow falls into an endless email loop, and
• when different users upload different files, each message lists every file as though every uploader added it.
All I really need is for the flow to fire once per upload, name the correct uploader, and then stop—no recycling, no cross-reporting. The incoming mail can stay one-email-per-file; I just want the looping behaviour gone.
You’ll receive a copy of the current flow (triggered by “When a file is created” and using standard Office 365 Outlook actions). Please identify the exact cause of the recursion, apply the fix—whether that means adding trigger conditions, concurrency controls, Do Until exits, unique IDs, or any other best-practice safeguard—and return a working version that I can import straight back into my tenant. A short note explaining the change set will help me support it later.
When you send your proposal, walk me through the approach you’d take and the specific adjustments you expect to make in the designer; the clearer your plan, the faster I can select and grant access.
Related categories:
.NET
C# Programming
Sharepoint
Microsoft
Office 365
Data Management
Power Automate
Microsoft 365