This has been acknowledged by recent "agy" release notes, it was timing out in client not in backend
Yup I use carbon hours daily with 10+ minutes between requests at the extreme without timing out. That timeout has to be the harness. I also haven't seen API errors since release day.
Yup I use carbon hours daily with 10+ minutes between requests at the extreme without timing out. That timeout has to be the harness. I also haven't seen API errors since release day.