[Feature Request]: twilio message create timeout about twilio-node

[thomas-topway-it]

hello, we have solved with a simple await instruction, apparently the app redirected to a new route before that the request was completed

[kareig]

going over source i see there are all the undocumented options i could use and will try them: options

[thomas-topway-it]

hello @kareig , we are having the same problem using it from svelte (vercel) server-side. Finally how have you solved it ?

Here is our import

import TwilioSdk from 'twilio';
const twilio = TwilioSdk(accountSid, authToken, {
  lazyLoading: false,
  autoRetry: true,
  maxRetries: 3,
  logLevel: 'debug',
});

[kareig]

Hi @thomas-topway-it,

Few things solved our issues we had:

1. adding timeout/retry on twilio client:

const twilioClient = context.getTwilioClient({
      autoRetry: true,
      maxRetries: 3,
      maxRetryDelay: 500,
      defaultTimeout: 1000,
    });

2. We also ship logs to external source so we had to set wait timeout for 1s for each callback, otherwise twilio function terminates immediately and no logs shipped to external endpoint:

return setTimeout(() =>
          callback(null, getSuccessResponse("SMS", messageSid), 1000)
        );

3. We also asked to extend timeout on our server-side vendor to wait for 10s from twilio (which is hard limit runtime) and only then timeout but with retries this probably does not make sense anymore.

Mostly timeout/retries for twilio client solved our issues because now we get a proper response from twilio client instantly and it does not hit a hard limit of 10s and runtime does not timeout without any response in case phone number is blocked or combination of twilio sender and receive is not allowed.

[tiwarishubham635]

Is this still an issue?