We’ve encountered a persistent issue when using the REST API step in WeWeb workflows with the “Proxy request server side” option (WeWeb Proxy).
Roughly 1 out of 10 identical requests fails with a “Network Error”, which completely breaks the workflow, no retries, no fallback.
This happens even on production, making flows unreliable and hard to control.
We’ve tested this multiple times: the same request, same setup, same endpoint, and still, 1 in 10 fails.
I’m sure we’re not the only ones experiencing this. If you run any production logic through this step, you’ve probably seen it too.
It’s clear this is not just a one-off or misconfiguration - it’s an issue within the proxy layer itself
Questions:
- Why does this happen?
- Is there any internal retry mechanism?
- How can we implement a proper retry or error handling strategy?
- Will this be fixed soon?
This kind of instability makes it hard to rely on the proxy for important steps.
Would really appreciate input from the WeWeb team and others who might have found a workaround or fix.
Thanks!
