WebSocket connection failure (wss://api-socket.mindstudio.ai) - reproducible across networks/browsers2

Bug Reports
1

Hi MindStudio team,

I’m experiencing a reproducible “Connection Failed” error when running workflows, and I’ve isolated it enough to be confident it’s server-side rather than something in my setup.

Console error:
WebSocket connection to ‘wss://api-socket.mindstudio.ai/’ failed
[Socket] WebSocket error event

What’s happening:

  • The workflow itself appears to execute correctly underneath, but the live-update socket drops. Clicking “Try again” sometimes reloads the next step, and screens with custom HTML menu blocks become fully unresponsive (no click or keyboard navigation registers) when the socket is down.
  • It occurs sporadically - sometimes at the very start of a run, sometimes mid-workflow at a custom HTML block.

What I’ve ruled out:

  • Tested on two separate networks (home connection and mobile hotspot) - same failure on both, ruling out my local network/firewall/ISP.
  • Tested on Chrome and Firefox - same failure on both, ruling out browser-specific issues.
  • Reproduced both directly in the MindStudio in-platform tester and via my live embedded site - ruling out my WordPress/embed integration.
  • Checked my account billing - current balance, no warnings, so this doesn’t appear to be a credits/billing issue.

This is affecting multiple workflows.

Could you please investigate on your end? Happy to provide screenshots, workflow IDs, or timestamps of specific failed runs if useful.

Thanks,
Rohan

2

Hi MindStudio team,

I’m experiencing a reproducible “Connection Failed” error when running workflows, and I’ve isolated it enough to be confident it’s server-side rather than something in my setup.

Console error:
WebSocket connection to ‘wss://api-socket.mindstudio.ai/’ failed
[Socket] WebSocket error event

What’s happening:

  • The workflow itself appears to execute correctly underneath, but the live-update socket drops. Clicking “Try again” sometimes reloads the next step, and screens with custom HTML menu blocks become fully unresponsive (no click or keyboard navigation registers) when the socket is down.
  • It occurs sporadically - sometimes at the very start of a run, sometimes mid-workflow at a custom HTML block.

What I’ve ruled out:

  • Tested on two separate networks (home connection and mobile hotspot) - same failure on both, ruling out my local network/firewall/ISP.
  • Tested on Chrome and Firefox - same failure on both, ruling out browser-specific issues.
  • Reproduced both directly in the MindStudio in-platform tester and via my live embedded site - ruling out my WordPress/embed integration.
  • Checked my account billing - current balance, no warnings, so this doesn’t appear to be a credits/billing issue.

This is affecting my live and public customer facing workflows.

Could you please investigate on your end? Happy to provide screenshots, workflow IDs, or timestamps of specific failed runs if useful.

Thanks,
Rohan

3

Hi @rohansimpson,

Thank you for the post, and I apologize for the inconvenience.

Could you share the agent IDs where the issue occurs? You can find each one by clicking the agent name and copying the ID at the bottom of the page:

image
image1286×893 112 KB

I’d also really appreciate it if you could make a quick screen recording of the steps leading up to the issue. You can use the link below to record your screen:

4

Hi @rohansimpson,

We’ve pushed a fix, so this should be resolved now.

Let me know if you notice anything similar going forward.

5

Seems rock solid now, thank you for your help. Phew!

7

I’m continuing to have the same problem. It wasn’t working, then a fix was pushed, then it was working but now today it’s not working again.