Why Did Some Bulk Send Recipients Fail?
A handful of failures in a big batch is normal: lists age, people leave companies, and limits run out. Inkfree records the reason for every failed row, so you never have to guess.
Before Anything Is Sent
Most problems are caught on the Recipients step, before you send: a missing name, an invalid email, a missing phone number for a role delivered by text or verified by SMS, or a value that does not fit its field. Inkfree flags those rows so you can fix or skip them. See how to prepare a recipient list.
Why Rows Fail During Sending
Open the batch from the Batches tab and it opens on Needs fixing. The What happened column gives each row's reason. The common ones:
- Your plan's envelope limit was reached. Each recipient uses one document from your plan. Inkfree refuses a send up front if your plan does not have enough documents left, so this only happens when your usage changes while the batch is still sending.
- Not enough SMS credits. Text delivery and SMS codes use SMS credits for every copy.
- This envelope could not be sent. A problem with that specific copy. The detail after the message says what went wrong.
Inkfree automatically retries a row up to three times for temporary problems before marking it failed.
Retrying Failed Rows
Once the batch has finished, fix the cause, then click Retry failed on the batch page. Inkfree resends only the failed rows, exactly as they are, so nobody who already received a copy gets a second one. Retrying checks your plan's documents, SMS credits and access codes again first.
Retrying cannot change a row's details. To correct an address, fix it in your file and start a new batch with just those recipients.
A Bounced Email Is Different
A bounce happens after a copy is sent, so it does not show as a failed row: the batch shows that copy as Sent. If a recipient says nothing arrived, follow what to do when a recipient didn't receive the document, then send them a new request at a current address.
Tip: Failure rate above a few percent? Your source list is probably stale. Clean it before the next batch rather than after.