Track a bulk send and retry failed rows

Every batch you send gets its own page with a live progress bar, a row per recipient, and the documents it created. When a row fails, the reason sits under its status and you can retry only those rows.

Who can do this

Available on Business and above. Batches are created in the wizard covered by bulk send from a CSV. You see the batches you are allowed to manage: admins see every batch in the workspace, managers see their teams', members see their own.

Follow a batch

1. Open Bulk sends. Each row shows the template name, a sent count such as 7/10 sent, and a status badge.

2. Click the batch you want. While it runs, a card at the top reads Sending envelopes with a progress bar and a processed count.

   

3. Use the Recipients tab for the row-by-row view: names, emails, a Pending, Sent or Failed badge, and an Open link to the document once it exists.

4. Documents lists the envelopes created so far with their signing status, and Activity carries the batch's own trail: created, started, finished, retried.

Closing the page changes nothing. Sending continues in the background, and the numbers are up to date whenever you come back.

Batch statuses

• Queued means it is waiting for a worker, usually for seconds.
• Sending means envelopes are going out now.
• Scheduled means it is waiting for the date and time you picked.
• Completed means every row went out.
• Completed with errors means at least one row failed while the rest succeeded.
• Failed means the batch itself could not run.

Deal with failed rows

A finished batch with failures gains two buttons in the header.

Failed rows CSV downloads exactly those rows with an extra error column, ready to fix in a spreadsheet. Retry failed rows puts them back in the queue as they are, leaving successful rows untouched, and asks you to confirm first. Retry when the cause was temporary, such as a limit that has since reset. Download and re-upload instead when the data itself was wrong, since retrying a typo in an email address fails again.

Common reasons a single row fails:

• Monthly document limit reached or the daily equivalent. Your allowance ran out partway through the batch.
• Unknown role. The template's roles changed after the batch was built, so a column no longer matches.
• Duplicate of an earlier row. Two rows aimed the same signer email at the same document.

Drafts and deleting

An unsent batch saved with Save & exit appears at the top of Bulk sends with a Draft badge, a Resume button and a bin icon to discard it. It is stored in that browser only.

Deleting a finished batch removes the record from the list. Documents it created stay in your account and carry on signing.

If something goes wrong

• The bin icon is disabled. The batch is queued or sending. Wait for it to finish, then delete it.
• Retry failed rows is missing. Either nothing failed, or the batch has not finished yet. Both buttons appear only once it settles.
• The progress bar looks stuck. Refresh the page. A batch that stopped for a limit shows the reason on its failed rows rather than in the bar.
• A draft vanished. You opened the app in a different browser or profile, or cleared site data. Drafts do not sync between machines.
• A retried row failed again. Its data is the problem, not the timing. Download the failed rows, correct them, and start a fresh bulk send.