- Issue created by @sah62
- 🇮🇱Israel jsacksick
Well, maybe we can increase it a little... To maybe 5 seconds, but in any case worst case scenario messages will be fetched on the next cron runs o it's no big deal.
- Status changed to Needs review
about 1 year ago 7:41am 4 January 2024 - last update
about 1 year ago 790 pass -
jsacksick →
committed e0b6c859 on 8.x-2.x
Issue #3412166 by jsacksick: GuzzleHttp\Exception\ConnectException: cURL...
-
jsacksick →
committed e0b6c859 on 8.x-2.x
-
jsacksick →
committed 113aa74a on 3.0.x
Issue #3412166 by jsacksick: GuzzleHttp\Exception\ConnectException: cURL...
-
jsacksick →
committed 113aa74a on 3.0.x
- Status changed to Fixed
about 1 year ago 7:32am 5 January 2024 - 🇺🇸United States sah62 US
Fix confirmed. I haven't seen any errors since deploying the patch.
Automatically closed - issue fixed for 2 weeks with no activity.