Outbound HTTP returns error 56 sometimes

We currently have a known issue with error 56 being returned in some circumstances; this is due to the server not knowing an HTTP/1.1 connection has gone stale, and so it attempts reuse and immediately fails. This usually happens when there’s light traffic to a server with more than 5 minutes idle time between requests.

It’s safe to immediately retry - you will get a fresh connection and the request should succeed.

We should be addressing this on the developer server later this week.

This should now be fixed for developer devices; we have migrated developer devices to a server running a build that has this issue addressed.

If anyone still sees this on non-production devices, please let me know.

This is now deployed to all servers.

That’s great news. Thanks for the update.