Testing Flow or Agent Deletes all Steps/Actions

(1) Share

Report

Posted on by SM-01042006-0

4 times today I have lost past flows or agents (that have multiple published versions)

When Hitting Save or Publish/Test it errors out and gives Request to Azure Resource Manager failed with error: '{"error":{"code":"WorkflowTriggerNotFound","message":"The workflow 'GUID Removed by me' trigger 'manual' could not be found."}}'.

When I then look at the Version History its empty.

This nuking of work is frustrating and defeats the enter point of the Paid Version of Studio. All we need to do is get user input and have it replace text in a sample word docx file and send it back to the user. works in some tests last week udpated the template to fix format issue and now have had the Studio nuke all the work we have done up till now.

Categories:

Topic creation & management

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Sunil Kumar Pashikanti 2,095 Moderator on at

Like (1)

Report
Copy link

Link copied!

Hi @SM-01042006-0,

This is a known Copilot Studio reliability issue, not user error.
When the internal Power Automate trigger becomes desynced (WorkflowTriggerNotFound), Copilot Studio can fail Save/Test/Publish and reload the agent with all actions removed and empty version history.
This is a backend/platform defect. Until resolved, the only safe mitigation is exporting flows, using solutions, and avoiding in‑place template edits during testing.

Version history doesn’t appear in Power Automate (flow inside a Solution): https://community.powerplatform.com/forums/thread/details/?threadid=96021e86-bb11-f111-8406-7ced8dcf6109

If you encounter the "Empty Version History," do not save again. Close the browser, clear your cache, and try to restore from a previously exported solution.

Was this reply helpful? Yes No
Suggested answer

Valantis 5,268 on at

Like (2)

Report
Copy link

Link copied!

Hi @SM-01042006-0,

Sunil's explanation is correct this is a confirmed backend desync between Copilot Studio and the underlying Power Automate flow trigger, not something you caused.

Did the restore from an exported solution work for you, or are you still stuck? If you don't have an exported copy to restore from, let us know and we can walk through what options are left.

Best regards,

Valantis

✅ If this helped solve your issue, please Accept as Solution so others can find it quickly.

❤️ If it didn’t fully solve it but was still useful, please click “Yes” on “Was this reply helpful?” or leave a Like :).

🏷️ For follow-ups @Valantis.

📝 https://valantisond365.com/

💼 LinkedIn

▶️ YouTube

Was this reply helpful? Yes No