web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Power Platform Community / Forums / Copilot Studio / New Workflows - Connec...
Copilot Studio
Suggested Answer

New Workflows - Connections Dropping

(0) ShareShare
ReportReport
Posted on by
Hi there! 

I have been working on flows within the new Early Release workflows, I am not using them for production, only to learn workflows well before it is utilised in General Release.

I have suddenly met the issue of an error occuring with node connections after an agent node.
An error will appear saying:

Edge 'edge-agent-07fc75ff-fbc9-4327-b35b-f177f46d3418-output-ifElse-8d7cc7d9-663d-4377-9751-faf95dde16d2-input' references handle 'output' which is no longer on node 'AGENT Email Extraction'. The connection will be dropped on save.

I built a successful flow and saved it, the next day this error appeared and the connection was gone between the nodes.
I tried removing and replacing the nodes but no luck.

Details of the flow:
When a new Email Arrives > Agent > If/Else > Two Agents Etc Etc

Image of the missing node connections:



















When I connect the node the error appears


Trigger Details:


Agent Details:

 
Categories:
I have the same question (0)
  • Suggested answer
    Nanit Khanna Profile Picture
    54 on at

    Hi,

    This looks like an Early Release workflow designer issue rather than a problem with your logic.

    The error:
    • “references handle 'output' which is no longer on node”
    usually means the Agent node schema/output changed internally after save/reload.

    Based on your screenshots:
    • The Agent node loses its output handle after reopening the workflow
    • Existing connections become invalid and are removed on save
    • Replacing downstream nodes usually does not fix it permanently

    Things you can try:
    • Delete and recreate the Agent node completely
    • Re-add the dynamic content (Body) manually
    • Save after each node addition
    • Avoid renaming nodes repeatedly
    • Create a fresh workflow and rebuild incrementally
    • Test with Prompt node instead of Agent node temporarily

    Important:
    • Early Release workflows are still experimental/pre-GA
    • Similar connection persistence issues have been reported by other users
    • Agent nodes currently appear less stable than standard connector/prompt nodes

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Users!

Kudos to our 2025 Community Spotlight Honorees

Congratulations to our 2025 community superstars!

Congratulations to the April Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Copilot Studio

#1
Valantis Profile Picture

Valantis 639

#2
Vish WR Profile Picture

Vish WR 293

#3
Haque Profile Picture

Haque 216

Last 30 days Overall leaderboard