CONNECTION Permission Issue - Can't use existing connection for Community Custom Connector

[ChristianRRL]

Hi there,

I'm not sure if this is a glitch or something changed, but when trying to setup a new Data Ingestion Custom Connector, I am running into an issue at the connection page due to not having CREATE_CONNECTION permission.

The thing is, I don't want to *CREATE* a new connection, I want to *USE* an existing connection, and after checking I confirmed I do have USE CONNECTION permission:

I find this very odd, because literally 1-2 days ago, I was able to create a new pipeline *USING* the existing connector.

[ChristianRRL]

+Additional context, following the same instructions on my ADM account. I do have the ability to "Create connection", but once again I can't find existing connections.

This is odd because (A) I should be able to leverage existing connections and not need to create a new one every time, and (B) both my ADM and regular accounts have the same access as far as I can tell.

... Wait, this is EXTRA WEIRD (writing in real time). I see my existing connections now after refreshing the page!

... Likewise, I went through the same steps on my non-ADM account. Originally, it came up just like I described originally (no existing connections came up). But after I refreshed the page, IT CAME UP!

Not even sure what to call this, but this seems like a genuine bug.

[balajij8]

Hi ChristianRRL,

Most likely a classic UI race condition or state management glitch with the UI which is common as Community Custom Connectors are in beta and under active development. Interfaces and behavior are subject to change.

What's likely happening here is that the initial page load is failing to fetch your existing connection metadata before rendering the component. Because the UI doesn't see any existing connections in that split second, it defaults to the fallback state of prompting you to create a new one. That immediately trips the CREATE_CONNECTION permission error since your role is properly restricted to USE CONNECTION.

Refreshing the page forces a clean state reload, allowing the backend API call to resolve properly and populate the drop-down. Your USE CONNECTION grant is perfectly fine, the workspace UI is just getting ahead of itself on the initial load.

You can document the behavior for your team and file a bug here.  If you are rolling this pipeline out to a production environment, keep an view on the behavior during updates as frontend caching and routing bugs like this are usually patched silently on the road to General Availability. You can try using Managed connectors if feasible.