Bulk send: job created but send unfinished

Bulk send creates a job, then walks unique emails. If start fails after create, the desk says Job created, but sending did not finish. Open that job and retry. Retrying skips rows that already sent. A sent row means the envelope exists. That is unfinished-job honesty: the CSV is not lost, a second upload is the wrong retry, and the banner is not the same sentence as HTTP 402 ENVELOPE_LIMIT.

Guessed columns are bulk send CSV column mapping. The month is bulk send Free envelope math. The job itself is bulk send for HR and sales envelopes. Desk help is Docs. This guide is the start-failed-after-create banner.

The FAQ says each unique address gets its own envelope. Features lists the same job under bulk send. Ask Inkpacket for bulk send job created but send unfinished to open this article. Ask how does bulk send work to open help. Ask csv send to open /desk/bulk. Those phrases stay on the product screens. This article is the public version of why you retry the job you already have.

Read the row, not the file

• Job created, but sending did not finish — the job exists. Open it. Retry. Skips rows that already sent.
• A sent row plus Invite email was not sent — the envelope exists. Copy that signing link. Do not upload the CSV again.
• A row that would exceed the month — HTTP 402 ENVELOPE_LIMIT. Same code as a single send. Later rows in that start did not go out.
• Duplicate emails in the list are sent once. A job accepts 100 unique emails.

Map the columns before you start. Preview the unique count. That preview is CSV column mapping. An optional access code (4–32 characters, no spaces) applies to every recipient in that job. Share it separately. The PIN is not in the invite email. If a signer then locks out, that is a 429 on unlock — access-code 429 versus API rate limit — not a reason to recreate the job.

What the banner is not

• Not Form closed. That sentence is a disabled Web Form slug.
• Not a seat refusal. Invite does not refuse when a workspace is full.
• Not Drive not configured. Archive waits for a completed envelope.
• Not a twin template. Use the workspace template you already picked.

If you needed strangers to start their own envelope, that is a Web Form, not a retry of this job — bulk send vs Web Forms. Saving a template does not count toward the monthly envelope cap. Each sent row does. A row that already went out already counted, even if mail skipped. The reminder interval and expiration you set on the job apply to every envelope that did go out. They do not apply to a row that never left create.

SMS on a bulk row follows the same soft-fail as a single send. Text-message (SMS) is coming soon. Reminders go out by email today and still shows the signing URL on that envelope. Drive archive still waits for completed. Do not treat an unfinished start as “the archive missed.” The envelopes that exist are the ones you can file later.

The click-path

1. Open Bulk send at /desk/bulk. If the banner says sending did not finish, stay on that job.
2. Retry. Do not paste the CSV into a second job “to be safe.”
3. For a sent row with no mail, open that document and copy the signing link.
4. If a row returns ENVELOPE_LIMIT, stop. Wait for the next UTC month. Checkout will not waive it.
5. On a phone, Bulk send is a drawer row — mobile desk hamburger menu map.

Ask Inkpacket for job created but sending did not finish to open this article. Ask how does bulk send work to open help. Marketing Ask stays site Q&A and deep links. It will not start the job from this article. Existing members sign in and open the same /desk/bulk row — the unfinished job is there whether you arrived from Features or from the drawer.

Caps and what is not open yet

Creating the job is not a send. Each sent row is. Free allows 5 packets a month. Free at 5 packets a month is the live cap desk send, bulk rows, Web Form fills, and API send share. Hitting it returns HTTP 402 ENVELOPE_LIMIT. Starter is 20 envelopes — more than Free — plus 3 published Web Forms. Seat counts are planning numbers; invite does not refuse when a workspace is full.

Billing is published, not charging. Checkout is not open. Text-message (SMS) is coming soon. Drive missing: Drive not configured. Stripe off: Payments not live. Those flags do not finish the walk or hide a sent row. The FAQ and More on bulk send use Job created, but sending did not finish in the same words.

Retry the job you have. Copy links on rows that exist. File those envelopes. Open a workspace on Free — see published pricing — and run one three-row throwaway so unfinished-job honesty is a banner you have already retried before a real roster hits it on a Tuesday.