I’d recommend setting your timeout to something like 60–90 seconds. The default 100 sec is usually fine, but if you’re seeing timeouts due to recent issues, lowering it a bit might help.
You can also implement retry logic, such as retrying failed requests 2–3 times with exponential backoff.
That way, if HubSpot is slow or having temporary issues, your code can handle it without needing long timeouts.
I’d recommend setting your timeout to something like 60–90 seconds. The default 100 sec is usually fine, but if you’re seeing timeouts due to recent issues, lowering it a bit might help.
You can also implement retry logic, such as retrying failed requests 2–3 times with exponential backoff.
That way, if HubSpot is slow or having temporary issues, your code can handle it without needing long timeouts.
I’d recommend setting your timeout to something like 60–90 seconds. The default 100 sec is usually fine, but if you’re seeing timeouts due to recent issues, lowering it a bit might help.
You can also implement retry logic, such as retrying failed requests 2–3 times with exponential backoff.
That way, if HubSpot is slow or having temporary issues, your code can handle it without needing long timeouts.
Thank you for the insightful recommendation on the timeout settings! I appreciate your suggestion to implement retry logic with exponential backoff as well. This will definitely help manage the variability in response times from the HubSpot API.
