Questions

Hi, This seems to be a long standing issue that has yet to have been addressed by Adobe in a public manner. It does not seem like the Auto-Complete data for Recipient email addresses can be cleared. After clearing browsing data, local adobe cache, and what accessible cloud data; the issue persists in that previously used email addresses/names are saved even if incorrect. A number of our Adobe Sign users are reporting issues of this persisting, with no ability to clear or remove any auto-complete options from the Adobe Sign Recipient fields; some entries are broken (incorrect name/incorrect email) others do not carry account information, some are duplicates with saved casing on the email address. Is there any means for Adobe to address this issue, or provide methods to address this issue, as this data does not seem to be accessible or stored locally.   Other related unresponsive posts:Solved: Email address autocomplete in Send & Track How can... - Adobe Support Community - 7969

Hi, I have a new Acrobat Pro account and everything is working but when I request signatures, it is adding [DEMO USE ONLY] Thanks

I'm sorry but your interface is confusing. I wish to send multiple independent copies to many recipients. But I need separate signatures, not everyone signing the same copy! The wizard kept blocking me, saying it needs to add signature blocks, although I had inserted two already 😞 Now everyone is seeing the same copy as a group!

Hi All,   We are using Adobe Sign for salesforce and generate our documents in salesforce however we are unable to create any documents from a salesforce record page any more as we get the Document Builder:INVALID_JOB_ID. Any thoughts on what to look for?       Thanks Abu  

 Hi Team , Noted there is an Error message on Salesforce for Adobe Document Builder :Invalid Job ID. Is there an ETA on when the Adobe Builder will be back up and the issue above will be resolved ? 

Usually when we send docs out, it comes adobesign@adobesign.com. Randomly this morning, one document sent came from: echosign@echosign.comcausing the document to be flagged by our system as "you don't often get mail from echosign@echosign.com", which concerned the recipient. Any explanation on why this would suddenly come through echosign instead of the usual Adobesign?

I have a cancelled agreement. It shows as cancelled in Adobe sign but it is still emailing reminders to the recipient. How do I stop those reminders from going out? 

Hi all, A client of ours is having some issues with Adobe Acrobat Pro/ DC Standard, where every time we click "request e-signatures" it loads for several minutes and then get an error stating "An error has occurred, please try again."  Several users at the company are experiencing the same issue. Here are the things I've tried so far: 1. Signing out of the Adobe app and signing back in2. Checking for available updates (app is up to date)3. Repairing the application4. Trying to request e-signatures through Adobe on the web (we received a similar error message)5. Rebooting the physical PC6. Deleting the below app data files: %appdata%\Adobe\Acrobat\DC\Security\acrobat_fss_signature_initials%appdata%\Adobe\Acrobat\DC\Security\acrobat_fss_signature_initialsi%appdata%\Adobe\Acrobat\DC\Security\acrobat_fss_signature_initialsk Nothing has worked so far, and the users are still experiencing the same issue when trying to request e-signatures. This is a feature they

Hi,We are using an AATL Doc signing certificate to sign documents and that works as expected for everyone within the company except one user. When opening his signed document, the validation fails. If someone send this user a signed PDF that leverages AATL, it fails and shows UNKNOWN. However, if this user runs Adobe Acrobat reader first and uses "Run as Admin" context, then the validation succeeds for his signed document and other docs signed by someone else.Has anyone seen this issue?__PRESENT

I am disappointed in the NEW (2025) Adobe Acrobat Sign experience online. I have had several issues with it, so I keep going back to the Classic experience. What I am noticing is, after I fill in the email address of who I am sending the document to, and then upload the template, it sends it to the user before I have even filled in the template with the data that I need.I have a blank template with fill in fields for items to check out to our users. With the classic experience I key in the email address to send to, I go to recent templates and attach the template, I then click send, it then loads the form for me to fill in the additional field data and then click send again and it sends.In the new experience, it doesn't allow me to fill in the fields with data, it just sends the template without any information keyed into it, but it doesn't actually send anything to the user. They receive nothing. I then have to go back on the browser, and fill in the data. Sometimes that works, b

porfavor su ayuda, no puedo agregra un archivo para enviarloa firmar, en mi compatura no me deja agregarlo usando la opcion de arrastrar y soltar, y en el telefono mobil si me deja agregar el archvio pero cuando hago el ultimo paso de mandarlo a firmar me manda un mensaje de que ocurrio un error y ya no se envia.

I want several people to sign a document but only after a (or two) person(s) has approved the document. My experience is that this only works in a specified order, i.e.1 - Approver approves2 - Signatory 1 signs3 - Signatory 2 signs4 - Signatory 3 signsand so on.However I want that the Signatories can sign the document in any order after approval by the Approver, i.e.1 - Approver approves2 - Signatories 1, 2, 3,... sign in any order Is that possible?

I work for a property management company and I require the e-signature feature. I have sent out around 70 files that need to be sent in 1 day, but I am now running into error 429 when I try to send additional ones. I am using the desktop version, and it's been over 12 hrs since running into this issue. I have restarted my laptop and I still continue to run into this issue.

Our customers are consistently getting an "unexpected error" when they sign our contract and attempt to make a payment through Adobe Sign. We have the payment integration with Braintree. We have been able to replicate the error on multiple browsers and devices. The error message shows up at the top of the popup payment window after clicking "Place Order and Sign", and does not include any other details (screen shot below). I would appreciate any pointers on how to resolve this. 

Has anyone had any luck with deleting the preset templates provided by Adobe?  This is causing confusion with users having access to these templates and would like these hidden/removed.  A support ticket did not resolve the issue.

For the last two days, my desktop client on macOS defaults to the Classic view, and it ruins my workflow. Sending a document for 3 signatures without templates was 7 mins before — now with classic view it's 25 mins. I tried to turn the new Reader off and back on again, restarting the desktop app — didn't help. I can't see any settings that could theoretically fix this. What's going on? Luckily, the web version works in the New mode, so I just installed the PWA app and will use it until the desktop client gets back to normal.

Hi, I am trying to set up a signature field in the document in Adobe Sign. The document is pre-signed by the other party, so I need to keep a record of this signature. Adobe perfectly recognized it (I cannot flatten the file in this case to solve the problem I explain further). The size of the document page in PDF is 8.5"x 11" (legal).When I open it in Adobe Sign to set up fields, I see the big text box with the main text with a scroller (so the full text is not visible on the page, you need to scroll it). The text is preset to Auto and Multiline. The signature field should fit in that text box, and I managed to add it there (first I placed it under the text box, and then dragged it over the text box). When I send the document for signature, the next signatory sees the text form that text box  in very small font, and the final signed document has it in a very small font, not the same as it looked in Adobe Sign. I tried to preset font size to 8 to make the scroller bar disappe

I'm reporting the same issue again as described here: Invalid digital signature on AcrobatDCx64Upd230082... - Adobe Product Community - 14246103 Some parts of the world are reporting different hashes for AcroRdrDCx64Upd2500120643_MUI.msp from both of the following download URLs: https://ardownload2.adobe.com/pub/adobe/acrobat/win/AcrobatDC/2500120643/AcroRdrDCx64Upd2500120643_MUI.msp produces a SHA256 hash of 2470FAE777456C31761DFC3E855386675E211BC7B099FDCAD1D17145FC272C22https://ardownload3.adobe.com/pub/adobe/acrobat/win/AcrobatDC/2500120643/AcroRdrDCx64Upd2500120643_MUI.msp with a SHA256 hash of 011095095184EF1AC0E8BEFEA29DE6239007272AD344F6287145595F546704B6 The problem can be observed from downloading in the UK. Downloads from Colorado (US) and Antwerp (Belgium) seem to download a file with a valid digital signature and SHA256 hash of 36523401F3484BC5F201D0A70620D73A5FF50926519696859F572F8E08CA1A34. We believe there is a

Hi there,Our NFP organisation requires a tool to request e-signatures.  I purchased Adobe Acrobat Standard but it stopped working - so I'm guessing that it has a limit (which I've tried to find in documentation, our account settings and even a phone call to Adobe only to be hung up on!). I'm quite frustrated that it's so difficult to get a product that is fit for purpose for our very cash-strapped organisation! Is it possible to purchase Adobe Acrobat Sign as a stand-alone subscription?  I've looked all through this community but the links are either dead-ends or are sending me to Adobe Acrobat Pro price comparisons.Please help me out here.MarciaPara Kore Marae

Hello, I am trying to integrate Adobe Sign with Salesforce for E-Signature. I have followed all the steps from the below Guide but still I am not able to see the button Send to Adobe Sign on Generate Document page in Salesforce. I have installed Adobe Sign Salesforce CPQ Connector version 1.8 and Adobe Acrobat Sign version 25.6.  Adobe Sign for Salesforce: CPQ (SteelBrick) Connector We had previously installed DocuSign a few years ago but discontinued it afterwards but the package is still there in our org. Could this be the reason behind this?

How to edit the period of the unsigned document expired. The documents have expired though one of the signers hasn't signed.I want to change the period. Please help.

I've managed to successfully create an Agreement via the API which has form fields assigned for each signer. I'm still getting the default Signature/Email fields added to a 2nd page - I don't really need the signer to complete these as I already have their details and they have already signed on one of the form fields. Is it possible when using form fields to have the default signature/email section not show: ? 

We had form recipients letting us know today that they could not seem to sign in the Initial portion of a document, and we tested ourselves and ran into the same problems on multiple platforms - both Firefox and Chrome browsers on mobile and desktop versions. Regular signing and misc form field entry seems to be fine, but when you click or tap on the Initial field, nothing seems to happen at all.

How do I stop an e-sign request I have sent out? It is no longer needed, but adobe keeps reminding the receiver, which they find irritating. 

I’m working with text tags in Adobe Sign and I’ve noticed different behavior depending on the field type and the source of the document:When the document comes from Word with text tags in the text (for example {{field_:checkbox}} or {{group_:radio:option}}), Adobe Sign correctly recognizes checkboxes and radio buttons. When I start from a PDF with form fields created in Acrobat (Prepare Form) and I only set the field name with the syntax (e.g. field_:checkbox or group_:radio:option), Adobe Sign does not recognize checkboxes or radio buttons.For text fields and drop-down lists, it does work, even if I create them as form fields in the PDF and just use the syntax in the field name.My question is:Is this a known limitation, that PDF form fields do not support text tag syntax for checkboxes and radio buttons?Is there any way to make Adobe Sign interpret them the same way as it does when they come from Word, or is the only option to use text tags directly in the text before generating the P