Timeout issue (BuildShip slow response) + Twilio workaround?
I have the "slow start" upgrade, but it seems like at least one of our workflows is still timing out at 15 seconds sometimes while Twilio is sending SMS messages to us. This is super critical because it means we essentially lose customer messages.
We need a more robust solution to this problem. Is there any way to ensure more robust delivery of messages, perhaps when BuildShip is having trouble, even if our customers have to wait that's ok.
I'm doubtful setting up a second endpoint that queues the response would fix this, but maybe it would? Maybe a proxy with retry logic (that seems like a feature request).
I've also considered setting up a Twilio function that retries the endpoint a few times, which might buy us more time.
Ideas welcomed!
We need a more robust solution to this problem. Is there any way to ensure more robust delivery of messages, perhaps when BuildShip is having trouble, even if our customers have to wait that's ok.
I'm doubtful setting up a second endpoint that queues the response would fix this, but maybe it would? Maybe a proxy with retry logic (that seems like a feature request).
I've also considered setting up a Twilio function that retries the endpoint a few times, which might buy us more time.
Ideas welcomed!
