This article will provide you with an overview of automated signature packet expiration for all signature providers and integrations.
You can automate the expiration of a signature packet, ensuring it expires a set number of days after being sent for signature—without requiring someone to manually trigger the expiration.
Refer to the table below for the range of days you can set for packet expiration with each eSignature provider:
| Provider | Valid Value Range (Days) |
|---|---|
| DocuSign | 1-365 |
| Adobe Sign | 1-180 |
| Dropbox Sign | 1-90 |
| Ironclad Signature | 1-365 |
Ironclad Signature
You can configure Automated Signature Expiration directly in Workflow Designer. For more details, see Customize Your Workflow Configuration.
Once set, expiration details will appear in the Activity Feed when a signature request is sent and when the packet automatically expires.
Click to Accept
Automated Signature Expiration is only available for the upgraded Click to Accept experience.
If Click to Accept is the default signature provider for a workflow, you can configure expiration settings directly in Workflow Designer. Expiration details will appear in the Activity Feed when a signature request is sent and when the packet automatically expires.
DocuSign, Adobe Sign, Dropbox Sign
Please check with your e-signature provider for additional details on how signature packet expiration works. While we make our best effort to expire packets based on the selected timeframe, the process is subject to the constraints of each third-party e-signature API.
Each configured expiration will appear in the Activity Feed when a signature request is sent and when we receive confirmation from the third-party provider that the packet has expired. For more details, refer to Configure Auto Expire.
Adobe Sign
During peak hours, Adobe Sign may take up to 12 hours to send a webhook confirming a signature request has expired. While the signing link will be deactivated immediately, the expiration will not be recorded in the Activity Feed until we receive confirmation from Adobe.
Dropbox Sign
Dropbox Sign rounds expiration times down to the nearest hour via its API. For packets set to expire in one day, we add one extra hour to prevent errors, which may result in expiration up to 60 minutes beyond 24 hours.
For example, if a packet is sent at 3:15 AM PST and set to expire in 1 day, Dropbox Sign would round the expiration down to 3:00 AM PST—less than 24 hours—causing the request to fail. To avoid this, we set the expiration for 4:15 AM PST, ensuring that when rounded down, it expires at 4:00 AM PST.
For packets set to expire in 2 days, Dropbox Sign will similarly round down the expiration to 3:00 AM PST on the second day.
DocuSign
DocuSign does not guarantee that a packet will expire exactly on time and states that the actual expiration event may occur up to 24 hours later (source). Additionally, we will override any admin default values for auto-expiration at the account level. For example, if a DocuSign admin has set packets to expire in 7 days but we receive a request to expire in 2 days, the packet will expire in 2 days. Likewise, if the default is 7 days and we receive a request to expire in 9 days, the packet will expire in 9 days.