Power Platform Community Forum Thread Details

Hello everyone,

We are experiencing a persistent UI rendering issue in the new Power Automate Designer. When we click on any Custom Connector action (e.g., our Jira-custom connector) to configure its parameters, the settings panel opens but is completely blank.

Key Observations:

The flow runtime is not affected. The flows are executing successfully.
Classic Designer works good. If we switch to the old designer, the custom connector parameters render and can be edited without any issues.
The issue strictly concerns the new UI rendering engine.

Browser Console Diagnostics:
When clicking on the Custom Connector action in the V3 designer, the browser's console shows the following explicit platform errors:

403 Forbidden from https://europe.api.powerapps.com/...
404 Not Found from Dataverse endpoints (https://org[REDACTED].api.crm4.dynamics.com/...).
These network failures immediately result in a React component crash on the frontend: Unhandled global error: ErrorEvent at 62.75e0738d.chunk.js.

Has anyone else encountered this specific blank panel issue for custom connectors in the new designer recently, or is there a known PG ticket / ETA for a platform patch for the Europe (crm4) region?

Categories:

Building flows

Using connectors

Hi @MK-16060906-0,

Your analysis is spot on. This is a known issue with the V3 designer where custom connector actions fail to render, while the flow itself continues to run correctly.

Since the Classic Designer works and runtime is unaffected, this confirms it’s a frontend/UI issue, not a problem with your connector.

What you can do
1. Use the Classic Designer
Switch back to the Classic Designer when you need to configure or edit custom connector actions. This is the most reliable workaround right now.

2. Check solution import issues (403/404)
If you are also seeing errors during deployment:

Make sure connection references are properly bound
Ensure your account has Environment Maker or System Customizer permissions
Verify the connector exists and is accessible in the target environment

3. Clear cache and refresh
Try a hard refresh or open in an incognito session to rule out cached schema issues.

When to escalate
If it still persists, raise a Microsoft support ticket and include:

Region (for example crm4)
Correlation ID from browser console

Summary:
This is a V3 designer UI bug affecting custom connector rendering. Use the Classic Designer as a workaround until the fix is rolled out.

✅ 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.

Sunil Kumar Pashikanti, Moderator
Blog: https://sunilpashikanti.com/posts/