Power Platform Community Forum Thread Details

Hello,

I am incredibly sorry to hear you are dealing with this. Experiencing a wiped canvas can be highly frustrating, especially when it happens repeatedly.

The good news is that because you can still see the successful data in your Previous Runs / Run History, your flow's logic is not completely gone—it is still cached in the Azure backend. The issue you are facing is likely a modern canvas rendering desync bug or an uncommitted solution layer conflict.

Here are the definitive steps to attempt a recovery and prevent this from happening again:

1. The Run History Recovery Trick (How to get it back

Since the version history fails to show the canvas, you can force the Power Automate/Copilot backend to clone a working instance from a successful historical run:

Go to the Run History page where you see the previous successful data.

Click on the specific Run ID of the last known working state of your flow.

Once the visual flow opens in "read-only" monitoring mode showing the successful execution path, look at the top command bar.

Click on Save As (or Clone).

Give it a new name (e.g., MyFlow_Recovered). This will generate a brand-new, fully populated canvas based on that specific historical run's schema, bypassing the corrupted canvas editor.

2. Check for Solution Layer Conflicts

If you are working within a Managed/Unmanaged Solution ecosystem, a "wiped clean" canvas usually means an unmanaged customization layer was deleted or overwritten by a failed publishing attempt.

Go to make.powerapps.com and navigate to Solutions.

Open the solution containing your Copilot agent/flow.

Select your flow, click the three dots (...), and look for Advanced > See solution layers.

If you see an unexpected "Active" unmanaged layer sitting on top of your base layer, it might be hiding your true canvas. You can investigate or remove conflicting layers to revert the canvas view to its last stable state.

3. Clear Browser Cache / Try InPrivate Mode

Copilot Studio heavily caches XAML/JSON canvas components in the browser's LocalStorage. If a test run crashes midway, the browser cache can render a completely blank canvas even though the cloud definition is intact.

Open an InPrivate/Incognito window, log into Copilot Studio, and check the topic/flow again. If it reappears, clear your main browser's cookies and cache.

Why does this happen during a Test?

This occurs when there is a schema mismatch between Copilot Studio's calling action and the input parameters expected by the underlying Power Automate flow. When you hit "Test," if the payload format fails abruptly before the execution handshake completes, the Studio editor sometimes fails to re-render the state tree, resulting in a blank visual canvas.

Recommendation: Moving forward, always ensure you hit Save explicitly in the top right corner before clicking the "Test" button to commit your canvas layout to the cloud database.

Please try the Run History > Save As method first, as it is the most reliable way to extract your lost logic. Let us know if you manage to restore it!

Best regards,