Power Platform Community Forum Thread Details

Hi,

The "Route did not match" error in the "Get file content" action typically occurs due to one of the following reasons:

Invalid File Identifier: The identifier passed to the action might not be correct or compatible with the Get file content action.
File Not Found: The file may not exist at the time the action tries to retrieve it.
Incorrect Dynamic Content: Using the wrong dynamic content from the Get files (properties only) step.

Here’s a step-by-step guide to troubleshoot and resolve this issue:

Steps to Resolve

1. Confirm the Output of "Get Files (Properties Only)"

Ensure that the output of "Get files (properties only)" includes the file you want to process.
Validate that the Identifier or Path of the file is returned correctly.
Add a Compose action immediately after Get files (properties only) to log and verify the file properties.

2. Use the Correct File Identifier

In the "Get file content" action, ensure you use the Identifier field (not the File Path or Name).
The Identifier is a unique reference for the file and is the most reliable way to fetch its content.
Dynamic Content Example:
- From Get files (properties only): Identifier
- For Get file content: Use the same Identifier.

3. Handle Subfolders in "Get Files (Properties Only)"

If your files are in subfolders, ensure that the "Get files (properties only)" action includes files in subfolders:
- Enable the Include Nested Items option in the action settings.
Ensure the folder path is correct when specifying the source location.

4. Add a Delay if Files Are Being Moved or Created

If files are moved or created in a previous step, add a Delay action (e.g., 5 seconds) before the "Get file content" action to ensure the file exists and is accessible.

5. Validate Folder Creation and File Availability

Verify that the file is actually moved to the newly created folder before "Get file content" is executed.
Add a condition to check if the file exists before trying to get its content:
- Use the "Get file metadata using path" action to confirm file existence.

6. Adjust Dynamic File Paths for Nested Folders

If you're dynamically creating folders, ensure the folder path is correct:
- Use dynamic expressions to construct the path for the "Get file content" action.

Example Dynamic Path:

Flow Overview

Here’s a simplified structure for your flow:

Trigger: When an email with attachments is received.
Action: Save attachments to the input folder.
Action: Get files (properties only) to list files in the input folder.
- Ensure nested files are included.
Action: Condition to check file existence (optional).
Action: Get file content using the Identifier field.
Action: Create a new output folder dynamically based on the email subject and date.
Action: Move the file to the newly created folder.

Troubleshooting Tips

Add Logging Actions:
- Use Compose actions to log the outputs of key steps (e.g., "Get files (properties only)" and "Identifier").
- Check the flow run history for values being passed to the Get file content action.
Review File Properties:
- Validate that the file you’re trying to access is listed in the Get files (properties only) output.
Check Permissions:
- Ensure the connection used in Power Automate has sufficient permissions to access and move files in the library.

----------------------------------------------------------------------------------
If this Post helped you, please click "Does this answer your question" and give it a like to help others in the community find the answer too!