Power Platform Community Forum Thread Details

I deployed an update for my verified connector (SimpleSurvey - Connectors | Microsoft Learn) on February 19 but as of today, the update is still not visible.
The update consisted of changes to the connector itself, not the API.

As per the official guidance, "once a connector is marked as Live, it can take approximately 10–14 days for the deployment to fully complete and for the updated connector to be available across all regions and services, including Power Automate. This deployment window applies to both new connectors and updates, as the connector goes through regional rollout and validation to protect platform integrity."

We are past this delay and I'd like to get some help on this please.

Categories:

Connector development

Hi @GN-11031831-0,

Here are the most effective steps to validate this:

1. Test in a Different Region
Global rollouts are staggered. Verify if the update is visible in a completely different environment region (e.g., if you are in US, try creating a test environment in Europe). If it's live there but not in yours, the sync is stalled for your specific geography.

2. Check the "Static" Connector vs. Connection
Sometimes the Connection object in your Power Automate flows remains bound to the previous version's metadata.

Create a brand new connection for the SimpleSurvey connector.

Build a simple "Instant" flow to see if the new actions or parameters appear.

3. Verify Versioning via CLI
If you use the Microsoft Power Platform CLI, run the following command to see exactly what version the platform thinks is current:
paconn download
Compare the downloaded JSON definition with your expected updates. If the downloaded file matches your old version, the deployment failed to propagate despite the "Live" status.

If all of these still show the old version, then the connector’s global rollout is stalled. Since you are already past Microsoft’s published 10–14 day deployment window for Live connectors, this requires direct escalation to Microsoft. Open a support ticket under Connectors > Custom/Verified Connectors, and optionally raise a GitHub issue on the official Connectors repo so the engineering team can investigate the stalled deployment pipeline.

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