## TL;DR

For "Error: timeout of 5000ms exceeded": upgrade to plivo-node 4.25.1 or later. The SDK imposed a fixed 5s timeout on the mass-text request, which is too short for a large destination list.

```text
Error: timeout of 5000ms exceeded
```

## Steps

1. The SDK imposed a fixed 5s timeout on the mass-text request, which is too short
for a large destination list. The bigger the list, the longer the request takes,
so it only breaks at scale.

2. Upgrade to plivo-node 4.25.1 or later. Plivo removed the fixed timeout for
messaging requests in that release.

3. Split the bulk send into smaller destination groups (about 500 numbers each),
or raise the axios timeout on the client. Prefer the upgrade.

## When to use

You are seeing this: Sending a bulk SMS to 1000 phone numbers through the Plivo Node SDK times out: `` Error: timeout of 5000ms exceeded `` from axios, even though the same rate worked before. Use this skill when you run into "Plivo mass text: timeout of 5000ms exceeded on bulk send".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

Versions mentioned in the source: plivo-node 4.25.1. If you are on something much newer or older, the details may have shifted.

## Why this happens

The SDK imposed a fixed 5s timeout on the mass-text request, which is too short for a large destination list.