[GH-ISSUE #626] [BUG] Error 500 when finish signing a document #172

Closed
opened 2026-02-26 18:45:42 +03:00 by kerem · 6 comments
Owner

Originally created by @lukasver on GitHub (Nov 3, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/626

Issue Description

Trying out the app.documenso.com app, created a test pdf document and sent it to 2 signers. When last signer of a document tries to confirm the signature, an error 500 is thrown in an HTTP call and submit button is stuck in infinite loading state.
When going to dashboard, the document appears as signed but an email is never sent to document issuer to notify all parties have signed.

Steps to Reproduce

  1. Create a document to sign in app.documenso.com.
  2. Send it to at least 2 recipients.
  3. Sign document as first recipient.
  4. Try to sign as second recipient and see error happening.

Expected Behavior

  • Error shoul be gracefully handled in frontend with some UI indicator and infinity loader should not happen.
  • Document sender should be notified if status is changed to completed.

Current Behavior

No response

Screenshots (optional)

image

Operating System [e.g., Windows 10]

MacOS Sonoma14

Browser [e.g., Chrome, Firefox]

Chrome

Version [e.g., 2.0.1]

No response

Please check the boxes that apply to this issue report.

  • I have searched the existing issues to make sure this is not a duplicate.
  • I have provided steps to reproduce the issue.
  • I have included relevant environment information.
  • I have included any relevant screenshots.
  • I understand that this is a voluntary contribution and that there is no guarantee of resolution.
  • I want to work on creating a PR for this issue if approved
Originally created by @lukasver on GitHub (Nov 3, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/626 ### Issue Description Trying out the `app.documenso.com` app, created a test pdf document and sent it to 2 signers. When last signer of a document tries to confirm the signature, an error 500 is thrown in an HTTP call and submit button is stuck in infinite loading state. When going to dashboard, the document appears as signed but an email is never sent to document issuer to notify all parties have signed. ### Steps to Reproduce 1) Create a document to sign in `app.documenso.com`. 2) Send it to at least 2 recipients. 3) Sign document as first recipient. 4) Try to sign as second recipient and see error happening. ### Expected Behavior - Error shoul be gracefully handled in frontend with some UI indicator and infinity loader should not happen. - Document sender should be notified if status is changed to completed. ### Current Behavior _No response_ ### Screenshots (optional) ![image](https://github.com/documenso/documenso/assets/63676303/1b97509f-73c7-4b78-bc64-b309d06c8a7e) ### Operating System [e.g., Windows 10] MacOS Sonoma14 ### Browser [e.g., Chrome, Firefox] Chrome ### Version [e.g., 2.0.1] _No response_ ### Please check the boxes that apply to this issue report. - [X] I have searched the existing issues to make sure this is not a duplicate. - [X] I have provided steps to reproduce the issue. - [X] I have included relevant environment information. - [X] I have included any relevant screenshots. - [X] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved
kerem 2026-02-26 18:45:42 +03:00
Author
Owner

@Mythie commented on GitHub (Nov 4, 2023):

Hey there, I remember this PDF it has security settings on it that mean it can't be updated or modified. I'll try and find the thread where I last worked with this but if you open the given test document in Adobe Reader you'll see the permission flags that have been set 😄

<!-- gh-comment-id:1793297035 --> @Mythie commented on GitHub (Nov 4, 2023): Hey there, I remember this PDF it has security settings on it that mean it can't be updated or modified. I'll try and find the thread where I last worked with this but if you open the given test document in Adobe Reader you'll see the permission flags that have been set 😄
Author
Owner

@Mythie commented on GitHub (Nov 4, 2023):

Can't find the thread anymore but if you see the flags set here you'll notice that modifications are disabled:
image

We are working on adding functionality to catch these kinds of documents and display an appropriate error or remove the restrictions.

<!-- gh-comment-id:1793303661 --> @Mythie commented on GitHub (Nov 4, 2023): Can't find the thread anymore but if you see the flags set here you'll notice that modifications are disabled: <img width="913" alt="image" src="https://github.com/documenso/documenso/assets/13398220/c451658b-3b9f-4d8f-8bd5-77c220f14455"> We are working on adding functionality to catch these kinds of documents and display an appropriate error or remove the restrictions.
Author
Owner

@poorna-prakash-sr commented on GitHub (Nov 5, 2023):

I can work on it

<!-- gh-comment-id:1793746598 --> @poorna-prakash-sr commented on GitHub (Nov 5, 2023): I can work on it
Author
Owner

@lukasver commented on GitHub (Nov 6, 2023):

Hey there, I remember this PDF it has security settings on it that mean it can't be updated or modified. I'll try and find the thread where I last worked with this but if you open the given test document in Adobe Reader you'll see the permission flags that have been set 😄

Woah! was not aware of this at all! thanks for clarifying!. i'll try again with a different pdf

<!-- gh-comment-id:1794667459 --> @lukasver commented on GitHub (Nov 6, 2023): > Hey there, I remember this PDF it has security settings on it that mean it can't be updated or modified. I'll try and find the thread where I last worked with this but if you open the given test document in Adobe Reader you'll see the permission flags that have been set 😄 Woah! was not aware of this at all! thanks for clarifying!. i'll try again with a different pdf
Author
Owner

@Mythie commented on GitHub (Nov 10, 2023):

I'm keeping this open so we can work towards improving the experience when dealing with documents with these protections enabled.

But I will be locking the thread for now until we return to this 🙌🏻

<!-- gh-comment-id:1804933954 --> @Mythie commented on GitHub (Nov 10, 2023): I'm keeping this open so we can work towards improving the experience when dealing with documents with these protections enabled. But I will be locking the thread for now until we return to this 🙌🏻
Author
Owner

@dguyen commented on GitHub (Nov 4, 2024):

Should be resolved now since we do a precheck to see if a document can be edited when it's initially uploaded.

<!-- gh-comment-id:2453735199 --> @dguyen commented on GitHub (Nov 4, 2024): Should be resolved now since we do a precheck to see if a document can be edited when it's initially uploaded.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#172
No description provided.