Adobe Acrobat Sign release schedule and prerelease documentation
Adobe Acrobat Sign rolls out at least three updates per year, categorized as major or minor releases. Additional minor updates may be introduced as needed to address system or customer issues.
- Major Releases bring significant updates, new features, and multiple enhancements.
- Minor Releases focus on smaller improvements and user experience tweaks. These occur between major updates, typically one to two times per cycle.
To prevent disruptions, new features are disabled by default and must be manually enabled by an account or group admin.
For Health and Life Sciences customers requiring compliance validation, Acrobat Sign partners with a third-party vendor to provide a validation package for every major release containing features to minimize your risk factor.
This Prerelease Notes page is regularly updated as new information becomes available, so its content is relatively dynamic.
While this page is localized, the process takes time, which may result in localized versions differing slightly from the authoritative US English version.
For the most accurate and up-to-date information, we recommend referring only to the US English page.
Adobe Acrobat Sign follows a structured schedule for publishing release notes and documentation updates:
8 Weeks Before Production Release
- The prerelease page publishes a summary of expected features and updates, typically four weeks before the Sandbox launch.
- Any feature changes after this point are noted in the Errata section.
- Resolved issues are not included at this stage.
4 Weeks Before Production Release (Sandbox Launch)
- The prerelease page is updated with detailed documentation on new and updated features.
- Links to prerelease support documentation (available in US English only) are added as needed.
- The initial Resolved issues section is published, with ongoing updates over the next four weeks.
Launch Day
- The official release notes are updated with final feature details and links to production support documentation.
- The prerelease page is refreshed to highlight the next release cycle.
- Documentation is published after release verification in the live system, typically after 7 pm PT, though complex updates may take longer.
- The final Resolved issues list is added to the US English release notes, with localized versions updated later.
Government Cloud Release
- The Government Cloud environment typically updates between two days and several weeks after the production release, as some features may require additional evaluation before deployment.
Sandbox documentation is designed for the production environment. Links found in the prerelease content target production URLs, meaning those links may lead to older existing documentation or 404 results if the target page is new and hasn't been published yet (e.g., when the link is pointing to a new feature in the same release).
The new pages will be published when the release is published, and links will properly resolve to their production URLs.
Sandbox availability
Customers accessing the Acrobat Sign Sandbox environment can typically access the new release functionality four weeks before launch.
- The Sandbox environment must pass all production quality assurance procedures at the same quality level as the regular production environment.
- Adobe strives to have 99.9% availability in the Sandbox environment, but customers should note that the Adobe Unified SLA does not formally cover the Sandbox.
- The Sandbox environment uses the same status page and outage procedures as the regular Production environment.
This article contains prerelease information. Release dates, features, and other information are subject to change without notice.
Sandbox deployment: October 7, 2025
Production deployment: November 4, 2025
GovCloud deployment: November 6, 2025
REST API/Webhook Updates
The below updates are presented in the prerelease notes for disclosure purposes. Full documentation for API and Webhook updates can be found in the Acrobat Sign developer documentation when the version update is delivered to the production servers.
- Webhook event for SMS delivery failures - A new webhook event for SMS delivery failures is available, providing a notification when a message can’t be delivered due to invalid numbers, carrier issues, or other problems. Notification is triggered after all retry attempts fail. This helps you quickly alert users, trigger retries, and keep agreements moving without delays—bringing SMS tracking in line with email bounce events.
Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: API
Release errata
There are no items that have slipped from this release as of this time.
Resolved Issues
| Issue | Description |
|---|---|
| 4509452 / 4526158 |
Summary: Searching for templates when creating agreements or Send in Bulk does not properly filter out other templates due to a component not properly indexing and scrolling |
| Fix: The faulty component has been corrected to ensure the search results are available. | |
| 4525233 | Summary: Agreements created with currency validation do not appear in the field as expected in the modern signing experience. |
| Fix: Currency-validated fields now correctly display the currency symbol once the field loses focus in the modern signing experience. The update ensures consistent symbol formatting across both classic and modern views. | |
| 4530694 | Summary: The wrong URL for "Change Password" link is embedded in the UI |
| Fix: The URL has been corrected. | |
| 4532664 | Summary: Signed PDFs generated from source documents that contain web link annotations may show “The document has been modified after signing” in Acrobat, and the Certification status appears invalid due to duplicate or malformed link annotations |
| Fix: Acrobat Sign now detects and correctly processes web links during the signing process, ensuring a valid certification status on the signed output. | |
| 4535715 | Summary: PDFs with web links double in size with each signature due to the printing function re-printing a copy of the web link annotation. |
| Fix: PDFs are now flattened to ensure no duplicate lins exist before merging annotations in the PDF. | |
| 4535760 | Summary: When using calculated fields that reference text input fields, some signed PDFs displayed incorrect or random numbers instead of the expected text value because the field engine attempted to convert text input to number or date formats. |
| Fix: The conversion logic in the calculated field engine was updated to recognize text-based inputs and bypass numeric or date parsing for those fields. | |
| 4536385 | Summary: Dropdown form fields with multiple widget annotations can not be an FT key or the generate appearance gets confused and thinks they are form fields. |
| Fix: The FT key has been removed from the widget annotations | |
| 4537356 | Summary: Templates shared with multiple groups were not displayed in the Send in Bulk page. |
| Fix: Updated the Send in Bulk logic to properly retrieve and display templates shared across multiple groups. | |
| 4537648 | Summary: The GET /agreements/{agreementId}/events endpoint listed a legacy event type "DOWNLOADED" in the Acrobat Sign REST API Swagger documentation. |
| Fix: The "DOWNLOADED" event type has been removed from the allowed values in the API documentation. | |
| 4537885 | Summary: Extra space appears on the Signature Preferences page |
| Fix: Removed the unnecessary spacer/div from the Signature Preferences layout container. | |
| 4538113 / 4538586 / 4543131 |
Summary: Multi-line, Auto Text Input Field form data shrinks to a very small size and becomes unreadable |
| Fix: Scaling has been corrected to not auto-shrink the font to an unreadable level. | |
| 4538340 | Summary: Signature metadata is being added without checking the field name |
| Fix: Added a check for the signature field to control the display of metadata | |
| 4538902 | Summary: The Get /agreements/memberSetInfo REST API endpoint returns incorrect agreement status and signer information. In some cases, the sender appears multiple times in the response, and participant data duplicates cause downstream integrations to fail. |
| Fix: The API now correctly returns agreement status and participant details without duplication. Each email address appears once per agreement, and signer information reflects the correct pending participant. No action is required from users. | |
| 4543085 | Summary: Older Salesforce integration versions (below v25.5) do not recognize the new status enums (COMPLETED and REMOVED) returned in webhook payloads. |
| Fix: Updated the Acrobat Sign REST API to exclude the new participant statuses and related enums when responding to older Salesforce integration clients. | |
| 4543951 | Summary: When editing a hyperlink field that has no title, saving the change creates a new blank hyperlink field instead of updating the original. Each save adds additional blank fields, making templates appear unchanged. |
| Fix: The update logic now correctly distinguishes between empty and null hyperlink titles, preventing duplicate fields. | |
| 4544118 | Summary: With Limited Document Visibility enabled in the new recipient experience, participant 2 could see hyperlink fields from participant 1’s document due to hyperlinks not being assigned. |
| Fix: Modern eSign now assigns and validates hyperlink fields like other fields and filters them by page and assignee. |
