UPDATE: Issue with Server Connect URL and Live Refresh With Sockets

In my test:
Update data (with security) --> Output data (with security) ~ Ok
Update data (without security) --> Output data (with security) ~ Ok

Update data (with security) --> Output data (without security) ~ Not ok

Not ok: I mean there’s no output, only preloader keeps loading and no error on console log either, no output from particular sc. Everything works fine when I remove the Live Data With Socket Attribute.

Can anyone confirm if this is the case or there’s problem with my setup?

Update: Hours testing multiple scenarios and comparing codes finally I found out the real issue - I’m not sure if it’s a bug or feature that being trigged the way I’m not aware of, so here the finding:-

DOES NOT WORK
<dmx-serverconnect id="output" url="/api/PS/output" sockets="true"></dmx-serverconnect>

DOES WORK
<dmx-serverconnect id="output" url="api/PS/output" sockets="true"></dmx-serverconnect>

See the difference? The one that doesn’t work has slash on url="/api/PS/output".

Since realizing this I’ve tried to reproduce the steps and whenever I select Action API Source from the SERVER CONNECT PROPERTIES > picker > Server Action it will include url with slash at the beginning.

I need confirmation from the team so calling @patrick to verify what’s going on here.

Thanks