User Guide Cancel

Adobe Acrobat Sign Release Schedule and Prerelease Notes

Last updated on Feb 17, 2026

Adobe Acrobat Sign

Open app

Adobe Acrobat Sign Guide

What's New

Get Started

Administer

Admin Console Overview
User Management
1. Add, edit, and review active users
2. Create function-focused users
  1. Technical accounts - API driven
  2. Service accounts - Manually driven
3. Review users who haven't completed verification
4. Check for users with provisioning errors
5. Change Name/Email Address
6. Edit a user's group membership
7. Edit a user's group membership through the group interface
8. Promote a user to an admin role
9. User Identity Types and SSO
10. Switch User Identity
11. Authenticate Users with MS Azure
12. Authenticate Users with Google Federation
13. Product Profiles
14. Login Experience
Account/Group Settings
1. Settings Overview
2. Global Settings
  1. Account tier and ID
  2. New Recipient Experience
  3. Self Signing Workflows
  4. Send in Bulk
  5. Web Forms
  6. Custom Send Workflows
  7. Power Automate Workflows
  8. Library Documents
  9. Collect form data with agreements
  10. Limited Document Visibility
  11. Attach a PDF copy of the signed agreement
  12. Include a link in the email
  13. Include an image in the email
  14. Files attached to email will be named as
  15. Attach audit reports to documents
  16. Merge multiple documents into one
  17. Download individual documents
  18. Upload a signed document
  19. Delegation for users in my account
  20. Allow external recipients to delegate
  21. Authority to sign
  22. Authority to send
  23. Power to add Electronic Seals
  24. Set a default time zone
  25. Set a default date format
  26. Users in Multiple Groups (UMG)
    1. Upgrade to use UMG
  27. Group Administrator Permissions
  28. Replace recipient
  29. Audit Report
    1. Overview
    2. Allow unauthenticated access on the transaction verification page
    3. Include reminders
    4. Include view events
    5. Include agreement page/attachment count
  30. Transaction Footer
  31. In Product Messaging and Guidance
  32. Accessible PDFs
  33. Healthcare customer
3. Account Setup / Branding Settings
  1. Overview
  2. Add logo
  3. Customize company Hostname/URL
  4. Add company name
  5. Post agreement URL redirect
4. Signature Preferences
  1. Well formatted signatures
  2. Allow recipients to sign by
  3. Signers can change their name
  4. Allow recipients to use their saved signature
  5. Custom Terms of Use and Consumer Disclosure
  6. Navigate recipients through form fields
  7. Restart agreement workflow
  8. Decline to sign
  9. Allow Stamps workflows
  10. Require signers to provide their Title or Company
  11. Allow signers to print and place a written signature
  12. Show messages when e-signing
  13. Require signers to use a mobile device to create their signature
  14. Request IP address from signers
  15. Exclude company name and title from participation stamps
  16. Apply Adaptive Signature Draw scaling
5. Digital Signatures
  1. Overview
  2. Download and sign with Acrobat
  3. Sign with Cloud Signatures
  4. Require digital signatures per recipient
  5. Include metadata for Identity Providers
  6. Restricted Cloud Signatures Providers
6. Electronic Seals
7. Digital Identity
  1. Digital Identity Gateway
  2. Identity Check policy
8. Report Settings
  1. New report experience
  2. Classic report settings
9. Security Settings
  1. Single Sign-on settings
  2. Remember-me settings
  3. Login password policy
  4. Login password strength
  5. Web session duration
  6. PDF encryption type
  7. API
  8. User and group info access
  9. Allowed IP Ranges
  10. Account Sharing
  11. Account sharing permissions
  12. Agreement sharing controls
  13. Signer identity verification
  14. Agreement signing password
  15. Document password strength
  16. Block signers by Geolocation
  17. Phone Authentication
  18. Knowledge-Based Authentication (KBA)
  19. Allow page extraction
  20. Document link expiration
  21. Upload a client certificate for webhooks/callbacks
  22. Timestamp
10. Send Settings
  1. Show Send page after login
  2. Agreement creation experiences
  3. Require recipient name when sending
  4. Lock name values for known users
  5. Allowed recipient roles
  6. Allow e-Witnesses
  7. Recipient groups
  8. CCs
  9. Required fields
  10. Attaching documents
  11. Field flattening
  12. Modify Agreements
  13. Remove recipients from in-flight agreements
  14. Agreement name
  15. Languages
  16. Private messages
  17. Allowed signature types
  18. Reminders
  19. Signed document password protection
  20. Send Agreement Notification through
  21. Signer identification options
    1. Overview
    2. Signing password
    3. Knowledge-based authentication
    4. Phone authentication
    5. WhatsApp authentication
    6. One-Time Password via Email
    7. Acrobat Sign authentication
    8. Cloud-based digital signature
    9. Digital Identity authentication
    10. Government ID
    11. Signer Identity reports
  22. Populate form fields with identity-verified data
  23. Content Protection
  24. Enable Notarize transactions
  25. Document Expiration
  26. Preview, position signatures, and add fields
  27. Signing order
  28. Add myself
  29. Download agreement link
  30. Form field borders
  31. Liquid mode
  32. Custom workflow controls
  33. Upload options for the e-sign page
  34. Post-sign confirmation URL redirect
  35. Restrict access to shared agreements
11. Message Templates
  1. Overview of Message Templates
  2. Creating new Message Templates
  3. Editing Message Templates
  4. Deleting Message Templates
12. Bio-Pharma Settings
  1. Overview
  2. Enforce identity authentication
  3. Signing reasons
13. Workflow Integration
14. Notarization Settings
15. Payments Integration
16. Signer Messaging
17. SAML Settings
  1. SAML Configuration
  2. Install Microsoft Active Directory Federation Service
  3. Install Okta
  4. Install OneLogin
  5. Install Oracle Identity Federation
18. Data Governance
19. Time Stamp Settings
20. External Archive
21. Account Languages
22. Email Settings
  1. Email header/footer images
  2. Permit individual user email footers
  3. Customize the Signature Requested email
  4. Customize the To and CC fields
  5. Enable Linkless Notifications
  6. Customize email templates
23. Migrating from echosign.com to adobesign.com
24. Configure Options for Recipients
Guidance for regulatory requirements
1. Accessibility
2. HIPAA
3. GDPR
4. 21 CFR part 11 and EudraLex Annex 11
5. Healthcare customers
6. IVES support
7. "Vaulting" agreements
8. EU/UK considerations
Download Agreements in Bulk
Claim your domain
Report Abuse links
System Requirements and Limitations
1. System requirements
2. Transaction limits

Send, Sign, and Manage Agreements

Recipient Options
1. Cancel an email reminder
2. Options on the e-signing page
Send Agreements
1. Send (Compose) page
  1. Overview of landmarks and features
  2. Group selector
  3. Adding files and templates
  4. Agreement name
  5. Global Message
  6. Completion Deadline
  7. Reminders
  8. Password protect the PDF
  9. Signature type
  10. Locale for the recipient
  11. Recipient signature order/flow
  12. Recipient roles
  13. Recipient authentication
  14. Private message for the recipient
  15. Recipient agreement access
  16. CC'd parties
  17. Identity check
2. Send an agreement only to yourself
3. Send an agreement to others
4. Written Signatures
5. Recipient signing order
6. Send in Bulk
Authoring fields into documents
1. In-app authoring environment
  1. Automatic field detection
  2. Drag and drop fields using the authoring environment
  3. Assign form fields to recipients
  4. The Prefill role
  5. Apply fields with a reusable field template
  6. Transfer fields to a new library template
  7. Updated authoring environment when sending agreements
2. Create forms with text tags
3. Create forms using Acrobat (AcroForms)
  1. AcroForm creation
  2. Creating accessible PDFs
4. Fields
  1. Field types
    1. Common field types
    2. E-signature fields
    3. Initials field
    4. Recipient name field
    5. Recipient email field
    6. Date of signing field
    7. Text field
    8. Date field
    9. Number field
    10. Checkbox
    11. Checkbox group
    12. Radio button
    13. Drop-down menu
    14. Link overlay
    15. Payment field
    16. Attachments
    17. Participation stamp
    18. Transaction number
    19. Image
    20. Company
    21. Title
    22. Stamp
  2. Field content appearance
  3. Field validations
  4. Masked fields values
  5. Setting show/hide conditions
  6. Calculated fields
  7. Verified forms
5. Authoring FAQ
Sign Agreements
Manage Agreements
Audit Report
Reporting and Data exports
1. Overview
2. Grant users access to reporting
3. Report charts
4. Data Exports
5. Rename a report/export
6. Duplicate a report/export
7. Schedule a report/export
8. Delete a report/export
9. Check Transaction Usage

Advanced Agreement Capabilities and Workflows

Webforms
Reusable Templates (Library templates)
Transfer ownership of web forms and library templates
Power Automate Workflows
1. Overview of the Power Automate integration and included entitlements
2. Enable the Power Automate integration
3. In-Context Actions on the Manage page
4. Track Power Automate usage
5. Create a new flow (Examples)
6. Triggers used for flows
7. Importing flows from outside Acrobat Sign
8. Manage flows
9. Edit flows
10. Share flows
11. Disable or Enable flows
12. Delete flows
13. Useful Templates
  1. Administrator only
  2. Agreement archival
    1. Save your completed documents to SharePoint
    2. Save your completed documents to One Drive for Business
    3. Save your completed documents to Google Drive
    4. Save your completed documents to DropBox
    5. Save your completed documents to Box
  3. Webform agreement archival
    1. Save completed web form documents to SharePoint Library
    2. Save completed web form documents to OneDrive for Business
    3. Save completed documents to Google Drive
    4. Save completed web form documents to Box
  4. Agreement data extraction
    1. Extract form field data from your signed document and update Excel sheet
  5. Agreement notifications
    1. Send custom email notifications with your agreement contents and signed agreement
    2. Get your Adobe Acrobat Sign notifications in a Teams Channel
    3. Get your Adobe Acrobat Sign notifications in Slack
    4. Get your Adobe Acrobat Sign notifications in Webex
  6. Agreement generation
    1. Generate document from Power App form and Word template, send for signature
    2. Generate agreement from Word template in OneDrive, and get signature
    3. Generate agreement for selected Excel row, send for review and signature
Custom Send workflows
Share users and agreements
1. Share a user
2. Share agreements

Integrate with other products

Acrobat Sign Developer

Support and Troubleshooting

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.

Note

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.

The prerelease schedule and notes are listed below.

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.

Note

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.

Releases

Alert

This article contains prerelease information. Release dates, features, and other information are subject to change without notice.

March 17, 2026 (Minor release) v17.0.1

Adobe Acrobat Sign release v17.0.1

Sandbox deployment: February 17, 2026

Production deployment: March 17, 2026

GovCloud deployment: March 19, 2026

Improved Functionality

Create a copy – Expanded access points, faster reuse of agreements.
Create a copy is now available directly from the In progress and Waiting for you filters on the Manage page, as well as from the post-send confirmation page. These additional entry points make it easier to reuse agreements at more points in the sending lifecycle, reducing the need to restart from scratch.
This feature will be available in the Sandbox environment on February 20, 2026.

Note: With this release, the administrative controls to disable this feature will be removed from the admin menu, establishing Create a copy as a standard capability available to all eligible users.
Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: Account and Group; Enabled by default.

Review the updated user action documentation >

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.

OEM 2.0 personalized email display – Clearer sender and recipient identity across embedded experiences, and correct email delivery.
For OEM 2.0 embedded workflows, Acrobat Sign now displays a user’s personalized email address instead of the partner-registered email across key UI surfaces and notifications. Agreements, queues such as “Waiting for you,” and “Review and Sign” emails consistently reflect the personalized identity while preserving the registered email internally for authentication and entitlements. This improves clarity for senders and signers and prevents emails from being sent to non-deliverable registered addresses.

Available environments: Sandbox, Commercial | Available tiers of service: Acrobat Sign Solutions | Configuration scope: API

Webhook notification for SMS delivery failures – Real-time visibility into failed SMS sends, automated remediation, and parity with email bounces.
Acrobat Sign now emits a new webhook event, AGREEMENT_PHONE_BOUNCED, when an agreement sent via SMS cannot be delivered due to issues such as invalid phone numbers, carrier rejection, or blocked lines. This enables customers to detect SMS delivery failures in near real time and automatically trigger follow-up actions like correcting phone numbers, retrying delivery, or opening support cases, eliminating blind spots and reducing delays in mobile-first signing workflows.

Available environments: Sandbox, Commercial, Government | Available tiers of service: Acrobat Sign Solutions | Configuration scope: API

Webhook payloads – Added conditional participant extendedStatus field for dynamic participation updates, improving participant state visibility.
Webhook notifications now include an extendedStatus field in each participant (memberInfos[]) object when the sender modifies an in-flight agreement using dynamic participation. This field provides additional participant lifecycle detail while leaving the existing status field unchanged for backward compatibility.

        {
          "participantSets": [
            {
              "id": "",
              "memberInfos": [
                {
                  "company": "TestCo",
                  "email": "signer2@someDomain.dom",
                  "id": "CBJCHBCAABAAJiZV9cH",
                  "name": "Signer Two",
                  "status": "ACTIVE",
                  "extendedStatus": "REMOVED"
                }
              ],
              "order": ,
              "role": "",
              "status": ""
            }
          ]
        }

status values (unchanged): ACTIVE, REPLACED.
extendedStatus values: ACTIVE, REPLACED, REMOVED, COMPLETED.

Available environments: Sandbox, Commercial, Government | 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
4543515	Summary: A webhook email bounce event may be incorrectly generated for a valid signer after the signer successfully signs and the agreement advances to the next step. This can occur when a delegatee in the same signing group has an invalid email address and the sender replaces the original delegator. In these cases, the system may incorrectly attribute the “signed on behalf of…” bounce event to the valid signer instead of the participant whose email actually bounces.
4543515	Fix: The event attribution logic was corrected so email bounce events are associated only with the participant whose email actually bounces. A bounce event is no longer generated for a valid signer who has already completed signing, and webhook notifications now reflect the correct participant and email address.
4544548	Summary: Integration Keys created through the Web UI may expire after 10 years, even though the creation page states that the key provides “permanent access.” When a key reaches its 10-year lifetime, API calls begin returning an expired token error, which may break existing integrations unexpectedly.
4544548	Fix: The user interface messaging was updated to remove the “permanent access” wording and clearly display the expiration date for Integration Keys. The updated text now states that the key retains access until the expiration date or until it is manually revoked, providing transparency about the 10-year default lifetime.
4546301	Summary: Webhook event delivery may be delayed by up to multiple hours for agreements with very large documents, even when agreement creation completes and early processing steps appear to finish within minutes. During the delay window, the webhook delivery service may repeatedly receive DOCUMENT_NOT_AVAILABLE responses when attempting to retrieve agreement documents, and the webhook event may not be delivered until the service stops retrying or the documents become available.
4546301	Fix: Document availability handling was corrected so large agreements reliably transition to a state where documents are retrievable without extended DOCUMENT_NOT_AVAILABLE responses. As a result, webhook events are delivered without multi-hour delays caused by document retrieval retries against unavailable documents.
4547823	Summary: A recipient's private message may not display for some signers when an agreement is created in the Authoring state through the API and then edited from the Manage experience. In this scenario, the UI may show the Private Message value as “None” or blank even though the agreement data includes the correct private message value. This behavior appears in shared-account scenarios where a user switches into another user’s account to edit the draft, and it may affect only specific recipients while others display correctly.
4547823	Fix: A check was added to retrieve the active share context and return the private message for authorized shared users. As a result, the Private Message value now displays correctly when viewing or sending an API-created draft from the Authoring flow.
4548274	Summary: The Modified Date for library templates may not update after a template is edited and saved in the new template experience. Users may see newly added or updated fields on the template, but the Modified Date remains unchanged in the Manage UI and in administrative views, which makes it appear that the template was not recently modified. This occurs because the new experience updates form fields through a path that does not also update the template’s modified timestamp.
4548274	Fix: The modified date update behavior was aligned across the new template experience and the related API operations. The code path that saves template field changes now also updates the template’s Modified Date so it reflects the actual time of the most recent change.
4548564	Summary: Signatures and form fields may appear invisible in the signed PDF when they are placed over pre-existing stamp annotations in the source document. In affected templates, the stamp annotations overlap or obscure the interactive fields during processing, causing completed signatures and other fields to be hidden in the final signed document.
4548564	Fix: Stamp annotation handling was updated to safely process and flatten pre-existing stamp annotations so they no longer obscure form fields or signatures. Fields placed over stamped areas now remain visible throughout signing and in the fully executed PDF.
4549103	Summary: An email bounce event may be logged again for a previously incorrect recipient after the sender replaces that recipient with a valid email address. In some cases, the audit trail may show a second bounce event for the old email, and the agreement status may reflect “email bounced” even though the new recipient successfully receives, views, or signs the agreement. This behavior can make it appear that the agreement is still targeting both the old and new email addresses.
4549103	Fix: The replace signer workflow was updated to prevent sending additional notification emails to a replaced recipient whose email has already bounced. The system now checks for prior bounce history before sending replacement-related notifications, ensuring that no new bounce events are generated for the old email address after replacement.
4549306	Summary: Users whose email addresses contain certain special characters (for example, an apostrophe) may be unable to log in from the generic adobesign.com or echosign.com public login pages. After entering the email address and clicking into the password field, the page may reload and clear the email field instead of redirecting the user to the correct shard or SSO login page. This prevents affected users from completing authentication and blocks integrations that rely on the public login endpoint.
4549306	Fix: The login shard resolution logic was corrected to properly handle and decode email addresses containing special characters before constructing the inter-shard redirect URL. Users with affected email formats are now correctly redirected to their designated shard and SSO login page without the email field being cleared.
4549331	Summary: Signatures and other form fields may appear missing or invisible in the signed PDF when certain document processing features are enabled and the source PDF contains invalid page box coordinates (for example, incorrect CropBox or MediaBox values). In this scenario, fields that rely on page coordinates may render outside the visible page area, making completed signatures appear missing even though signing completes successfully.
4549331	Fix: PDF page box handling was corrected to safely normalize invalid CropBox and MediaBox values during document processing. As a result, signature and form field placement now aligns to the visible page area, and signed PDFs display signatures as expected.
4550367	Summary: Creating a web form may fail with a generic “Server error” after selecting Preview and Add Fields when the sender’s group default signer authentication is set to Phone and the account does not have available phone authentication quota, even if the web form signer authentication is set to a non-phone method (for example, Adobe Sign). As a result, all users in the affected account may be blocked from creating web forms across all documents.
4550367	Fix: Web form creation now evaluates quota only for the authentication method actually configured for the web form signer, and it no longer applies phone authentication quota checks based solely on the group default authentication setting. This prevents false quota exhaustion errors and allows web forms to be created normally.
4551011	Summary: When a sender uploads certain scanned PDFs, adds signature fields, and sends the agreement, the signed PDF may display no visible signatures after signing completes. This behavior may occur when the uploaded PDF contains invalid page boundary metadata (MediaBox and CropBox coordinates appear reversed), which can cause signature and other field appearance layers to render outside the visible page area.
4551011	Fix: PDF page boundary handling is updated to correctly process PDFs with invalid or reversed MediaBox and CropBox coordinate values, so signature and form field appearance content renders within the visible page area and remains visible in the final signed PDF.
4551427	Summary: Some recipients who already have active, correctly provisioned accounts receive agreements as “pseudo user” recipients instead, so the agreement does not appear in their normal Manage view. This happens when recipient email addresses include leading or trailing spaces, which prevents the system from matching the email to the existing user and causes a pseudo-user record to be created.
4551427	Fix: Email parsing and user lookup were updated to normalize recipient email addresses (trim leading and trailing whitespace) before matching them to existing users. As a result, agreements addressed to existing users resolve to the registered account instead of creating a pseudo-user recipient, even if the email was entered with spaces (in API payloads and workflow recipient lists).
4553198	Summary: When an agreement includes at least one recipient configured for SMS delivery and at least one recipient configured for email-only delivery, canceling the agreement through the API does not send an SMS cancellation notification to the SMS recipient. The agreement is successfully cancelled, and email notifications are delivered, but SMS recipients do not receive a cancellation message.
4553198	Fix: The cancellation workflow was corrected to ensure that SMS cancellation notifications are sent to all recipients configured for SMS delivery when an agreement is cancelled, regardless of other recipients’ delivery methods.
4554463	Summary: When agreements include cloned radio buttons that share the same field name across combined documents, only one instance of the selected option remains selected in the final signed PDF. Although the fields appear visually as checkboxes, they are implemented as radio buttons. After signing, the selected value does not consistently propagate across all cloned instances, causing incorrect or incomplete mapping of the expected selection.
4554463	Fix: The form field handling logic was corrected so that cloned radio buttons store and propagate the selected export value rather than an internal index value. This ensures that all cloned instances of the same radio button field reflect the correct selection in the signed PDF.
4554593	Summary: Some partner integrations that use the legacy OAuth endpoints to refresh access tokens started failing with HTTP 401 errors. The service rejected token refresh requests with an error indicating that the application is not allowed to use the legacy OAuth endpoints and must use the OAuth v2 endpoints instead. This blocked customers from authenticating Acrobat Sign through partner applications, even for integrations that were previously working.
4554593	Fix: The authentication service was corrected so partner applications that are configured to use the legacy OAuth flow can successfully refresh tokens again, instead of being incorrectly forced onto the OAuth v2 endpoints.
4554614	Summary: When a signer uses the modern eSign experience on an agreement that requires signer authentication and is configured to require acceptance of terms of use before signing, clicking Click to Sign triggers a 5-second redirect to the classic signing experience. The redirect message warns that signatures and initials entered in modern signing will be cleared, forcing the signer to re-enter them and effectively sign twice.
4554614	Fix: The signing token refresh flow was corrected so that when the signer accepts the terms of use before signing, the reissued signing token retains the signer authentication details. This prevents the final signing step from failing authentication and eliminates the forced fallback from modern signing to the classic experience.
4555656	Summary: Under specific timing conditions, an agreement state transition may appear to succeed but does not actually change the agreement state. When a webhook notification is received before backend processing completes, subsequent API calls can use stale agreement status data. In this window, certain state transition methods return HTTP 200 OK even though the agreement is not in a valid state for the requested transition. As a result, automation workflows may assume the transition succeeded while the agreement remains in the original state.
4555656	Fix: Agreement state transition logic was updated to enforce strict validation before applying a transition. If the agreement is not in a valid state, the API now returns a clear error response instead of silently returning success. This ensures invalid transitions are explicitly rejected, enables calling systems to retry appropriately, and prevents agreements from remaining in an unintended state without visibility.