Socket hang up issues

I would be curious from an eng perspective about the diagnosis/RCA once y'all have it. I understand that this can't always be shared, but just in case it can be, would love to know!

1 Like

We've been seeing an increase in these types of errors as well. In the affected workflows, we have some Python blocks that cannot be converted to JS. All loops in the workflows are running JS or workflows (the workflows they run also use Python blocks that we cannot convert). Has a root cause been determined that we might be able to work around while maintaining Python in the workflows?

1 Like

This has come up for me a second time, in a different workflow, with workflow runid of 0197ed61-c963-72eb-8c0a-379fcd6965b0

any update here? this is immensely frustrating and a big blocker to our company moving entirely to retool.

1 Like

+1 on this issue. Huge blocker to continue using Retool.

2 Likes

+1. Same issue happening here.

1 Like

Appreciate all the bumps, everybody! I can certainly understand any frustration you're feeling, but we're committed to diagnosing this and will be prioritizing a deeper investigation in the coming weeks.

Because certain backend server logs are only retained for 30 days, it would be super helpful to get the following for any recent occurrences of this error that you've observed:

  • the relevant workflowId
  • the relevant workflowRunId
  • a summary of the workflow or JSON export

Feel free to DM me. :+1: