Power Platform Community Forum Thread Details

Hi,

Solution 1: Batch Processing with Parallel Branches (Recommended)

Replace your current "For each" loops with parallel branches:

When a new email arrives
├── Compose folder name
├── Compose file path
├── Create new folder
├── Create sharing link
└── Parallel Branches (Split attachments into batches)
    ├── Branch 1: Process attachments 1-3
    ├── Branch 2: Process attachments 4-6
    ├── Branch 3: Process attachments 7-9
    └── Branch 4: Process attachments 10+

Implementation:

Split attachments array using take() and skip() functions

Create 3-4 parallel branches to process attachments simultaneously

Each branch processes 3-5 attachments in a smaller "For each" loop

Expression Examples:

Branch 1: take(triggerOutputs()?['body/attachments'], 3)

Branch 2: take(skip(triggerOutputs()?['body/attachments'], 3), 3)

Branch 3: take(skip(triggerOutputs()?['body/attachments'], 6), 3)

Solution 2: Eliminate Redundant Actions

Current Flow Issues:

Creating sharing link for EACH attachment (unnecessary)

Individual folder creation calls

Separate compose actions for each attachment

Optimized Flow:

When a new email arrives
├── Compose folder name (once)
├── Compose base file path (once)
├── Create new folder (once)
├── Parallel Attachment Processing
└── Create sharing link (once, at the end)

Solution 3: Use SharePoint REST API Batch Requests

Replace individual "Create file" actions with batch upload:

HTTP Action - Batch Upload

Method: POST
URI: _api/$batch
Headers:
{
  "Accept": "application/json",
  "Content-Type": "multipart/mixed; boundary=batch_[guid]"
}
Body: [Batch request with multiple file uploads]

Benefits:

Single API call for multiple files

Reduced network overhead

Faster processing

Solution 4: Conditional Large File Handling

Add file size checking to handle large files differently:

Condition: length(triggerOutputs()?['body/attachments']) > 10MB
├── True: Use chunked upload for large files
└── False: Use standard upload

Large File Upload Method:

Method: POST
URI: _api/web/GetFolderByServerRelativeUrl('[folder-path]')/Files/StartUpload(uploadId=guid'[new-guid]')

Solution 5: Optimized Flow Structure

Complete Optimized Flow:

When a new email arrives (V3)
├── Initialize variable - Email ID
├── Initialize variable - Folder Name
├── Initialize variable - Attachments Array
├── Compose - Create folder path
├── HTTP POST - Create folder (single call)
├── Condition - Check attachment count
│   ├── ≤ 5 attachments: Standard processing
│   └── > 5 attachments: Parallel processing
├── Parallel Branches (for > 5 attachments)
│   ├── Branch 1: HTTP POST Batch Upload (files 1-5)
│   ├── Branch 2: HTTP POST Batch Upload (files 6-10)
│   └── Branch 3: HTTP POST Batch Upload (files 11+)
└── HTTP POST - Create sharing link (once)

If I have answered your question, please mark it as the preferred solution ✅ . If you like my response, please give it a Thumbs Up 👍. Regards, Riyaz