Web Form reminders and expiry on publish

When you publish a Web Form you can set reminder days and expiration on that form. Reminder days accept 0–90. Expiration accepts 0–365. Every later fill inherits that pair. Envelopes already created keep the days they were born with. Changing the published form does not rewrite last week’s envelopes. That is publish-cadence honesty: the slug stores the defaults; the envelope stores the window it was born with.

Publishing the slug is publish a Web Form from a template. Weekly operations after that are operating a Web Form share link. The two send fields on a desk envelope are reminder cadence versus envelope expiry. Picking a window is how to choose an envelope expiry. Desk help is Docs. This guide is the pair you set on publish — not the pair on Documents → new.

The FAQ states the same optional reminder days and expiration on the form. Features names them under Web Forms. Ask Inkpacket for set web form reminder to open the desk. Ask how Web Forms work for help. Those phrases stay on the product screens. This article is the public version of inheritance.

What you set on publish

• Reminder days — 0–90. 0 skips nudges on fills born after that setting.
• Expiration — 0–365. 0 means the fill’s signing link does not expire.
• An optional access code. The PIN uses the same five-try, 15-minute lockout as an envelope code.
• Publish is not a send. A later fill that goes out is the envelope.

A desk send uses workspace defaults from Settings #cadence — every 3 days, 14 days until the link dies — unless you override them on that envelope. A Web Form does not read Settings #cadence for each stranger. It reads the numbers you stored on the form. If you want fills to nag every 3 days and die in 14, set 3 and 14 on publish. If you leave them empty or zero, you are choosing that outcome on purpose.

Inheritance, not rewrite

Monday’s fill keeps Monday’s window. Tuesday you change the form to 7 and 30. Wednesday’s fill gets 7 and 30. Monday’s envelope does not move. Do not open Envelope admin on Monday’s id expecting the new numbers. Do not void Monday because the form changed. File Monday on the days it was born with.

Closing the form stops new fills. It does not expire envelopes already created. Public form closed copy is that door. Existing signers still finish — unless you void that envelope or its own window ends.

After the fill

A scheduled job emails outstanding SENT envelopes when the inherited interval has elapsed. If Resend is missing, the reminder is logged the same way as the first invite. The envelope stays SENT. The fill page already said The invite email was not sent. Use the signing link below. Copy that link from the envelope, not from the slug. A reminder is not a second fill and not a second envelope.

After expiry the desk shows expired status. The signer sees This signing link has expired and cannot complete the envelope. Embed uses the same token. Envelope admin cannot void, correct, or resend an expired envelope. Ask for a new envelope if the work still needs a signature — that new send is a new envelope toward the monthly cap. The hourly cron marks overdue SENT envelopes expired so the document list stays honest. Document list aging and status honesty is that list.

The PIN is not cadence

Share the optional access code separately from /form/SLUG. A public page plus a PIN in the same paragraph is not a second factor. After five wrong guesses the form returns HTTP 429. That is a Web Form PIN lockout, not an expiry and not ENVELOPE_LIMIT. Access-code lockout recovery is the wait.

The click-path

1. Save a template with at least one field. Publish at /desk/forms#publish.
2. Set reminder days (0–90) and expiration (0–365) before you share the slug.
3. Share /form/SLUG. Preview traffic is not an envelope; submit is.
4. Leave already-created envelopes on the days they inherited.
5. Disable the form when the cohort is done. Do not publish a twin slug to “change cadence.”

A second publish spends a published-form slot. Free includes 1 published Web Form. Hitting that gate returns HTTP 402 and names the plan limit — not ENVELOPE_LIMIT. Web Form Free published-form cap is that 402. Disable the form you have, then re-enable if the same slug should take fills again with the new pair.

Caps and what is not open yet

Publish is not a send. A fill that goes out counts. Free allows 5 packets a month. Free at 5 packets a month is the live cap this fill shares with desk send, bulk rows, and API send. 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 rewrite last week’s inherited days. The FAQ and reminders on Features keep cadence and expiry as two jobs.

Set the pair on publish. Share the slug. File each completed fill from its envelope — the form was only the door. Open a workspace on Free — see published pricing — and publish a throwaway with interval 0 and a short expiry so both inherited outcomes are something you have watched.