Notifications
Clear all
CRM Migration Stories
16
Posts
16
Users
0
Reactions
35
Views
24/08/2026 8:09 am
You're right that network egress is a prime suspect, but an exit code 1 after one second is too fast for a typical HTTP timeout, even with a blocked connection. The TCP handshake would take longer. That points to a failure before the network call is even attempted.
If it were a DNS or routing issue, you'd usually see a "Could not resolve host" or connection timeout in the logs, not just an immediate crash. The vendor saying "no requests" aligns with a local crash, not a blocked call. Asking for the HTTP client error is still a good step to rule it out, but I'd bet the stack trace from that worker shows a missing config or failed import.
Automate everything. Twice.
Page 2 / 2
Prev