Power Platform Community Forum Thread Details

Hi everyone,

I’m building a workflow using Microsoft Power Automate, SharePoint, and Microsoft Teams, and I’m facing an issue in the final step of the process.

Scenario:

A meeting recording file is generated from a Teams meeting and initially stored in OneDrive/SharePoint.

The file is then moved into a designated SharePoint folder (central repository).

A flow is triggered when the file is created in this location.

The flow sends a Teams Adaptive Card requesting multiple inputs (e.g., Name, Date, Project, etc.).

After the user submits the response:

A subfolder is created dynamically (based on input, e.g., Name/Project).

The file should then be moved into that subfolder and renamed (e.g., Name_Date).

Current Status:

✅ Trigger is working correctly

✅ Adaptive Card is sent and response is captured

✅ Folder is being created successfully

❌ File is NOT moving to the destination folder after this step

Issue:

Even though all prior steps are working, the file move action either:

Fails silently, or

Does not move the file to the newly created folder

Test works perfectly

17745235540907513...

Your file is currently under scan for potential threats. Please wait while we review it for any viruses or malicious content.

Categories:

Power Automate Desktop

Building flows

Power Automate Mobile App

Hi @CU24032155-0,

Your flow completes all logic steps (trigger, adaptive card, folder creation), but the file fails to move after the Teams Adaptive Card response. This is a known Power Automate pattern issue, typically caused by using incorrect file identifiers, timing/locking issues, or moving the file while still referencing the original trigger context. Because the test run works but live runs fail, this is not a permissions issue, it’s a file reference and timing problem.

Why the file doesn’t move

1) The “Move file” action is using the original trigger file ID, but after the adaptive card wait and folder creation, that ID may be stale or locked.
2) Teams meeting recordings are often still finalized or indexed when the flow attempts to move them.
3) “Get file content” is unnecessary and can break the reference chain.

How to fix it

Remove “Get file content”, it’s not needed to move files.
After folder creation, add “Get file metadata using path” (or “Get file metadata using ID”).
Use the returned Identifier from that step in Move file.
Add a Delay (30–90 seconds) after the adaptive card response (Teams recordings are often locked).
Ensure the Destination Folder Path exactly matches the newly created folder path.

Best‑practice move pattern

Trigger
→ Adaptive Card
→ Create Folder
→ Delay (optional but recommended)
→ Get file metadata using path
→ Move file (use Identifier from metadata step)

The flow logic is correct, the failure is due to file ID reuse + timing. Refresh the file reference after the adaptive card and add a short delay, and the move will work reliably.

✅ If this answer helped resolve your issue, please mark it as Accepted so it can help others with the same problem.
👍 Feel free to Like the post if you found it useful.