Sign Document: I can't send my Sign Document

  • coralcove23
    Asked on August 1, 2025 at 2:51 AM

    I have tried resetting the cache but I still get the same error


    Jotform Thread 29625041 Screenshot
  • Lorevie JotForm Support
    Replied on August 1, 2025 at 3:12 AM

    Hi coralcove23,

    Thanks for reaching out to Jotform Support. I was able to open the Send to Sign section of your Sign Builder. Check out my screenshot below:

    Sign Document: I cant send my Sign Document Image 1 Screenshot 30I was also able to send a sign document from my sample document. Check out my screencast below:

    Sign Document: I cant send my Sign Document Image 2 Screenshot 41 Can you give us a detailed explanation of the issue? When do you experience the issue? Is this when you open the Send tab? Or is it after clicking on the Send to Sign button? Can you try to clear your browser caches, then log out and log back in to your account? Can you also try it on a different browser? I've also gone ahead and cleared your form caches. Can you try it again?

    If the issue persists, can you create a link and manually send it to the signer? Let me show you how to do this:

    1. In Sign Builder, click on Send on the green navigation bar at the top of the page.
    2. Next, on the left side window, click on Share with link.
    3. Then, select a signer from Who are you creating this link for?
    4. From Specify other signers, enter the email address of the other signer and click on Create Link.Sign Document: Getting an error message when sending the document Image 2 Screenshot 51 Screenshot 52
    5. Click on the Copy Link button and manually send it to the signers.Sign Document: Getting an error message when sending the document Image 3 Screenshot 62 Screenshot 63

    If the same thing happens, can we send the document to our email address to see if we can replicate the issue?

    Keep us updated and let us know how it goes.

  • Lorevie JotForm Support
    Replied on August 1, 2025 at 3:50 AM

    Hi coralcove23,

    I just heard from our developers that the issue has been fixed now. Can you check on your end if it's working now?

    Keep us updated and let us know how it goes.

Your Reply