starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 13:55:59 +03:00

[GH-ISSUE #1714] How to restart pending document to finish? #488

New issue

Closed

opened 2026-02-26 18:47:15 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 18:47:15 +03:00

Owner

Originally created by @ASchmidt84 on GitHub (Mar 17, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/1714

Hi.
I had to add "- NEXT_PUBLIC_DOCUMENT_SIZE_UPLOAD_LIMIT=25" to my docker env.
Now i could edit my on document (for testing) and it worked.
Is it possible that the old pending documents (which are all finished but only had errors in processing) to restart the finish process?

Thank you.

Originally created by @ASchmidt84 on GitHub (Mar 17, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/1714 Hi. I had to add "- NEXT_PUBLIC_DOCUMENT_SIZE_UPLOAD_LIMIT=25" to my docker env. Now i could edit my on document (for testing) and it worked. Is it possible that the old pending documents (which are all finished but only had errors in processing) to restart the finish process? Thank you.

kerem

2026-02-26 18:47:15 +03:00

closed this issue
added the
status: triage
label

kerem commented

2026-02-26 18:47:16 +03:00

Author

Owner

@dguyen commented on GitHub (Mar 18, 2025):

You should be able to do this through the admin panel which lets you find a document and "reseal" it.

To access the admin panel, you need to update a user account to have the "ADMIN" role. You'll need to do this by connecting to the database and editing the user role manually.

From then, you can access the admin panel in the top right menu using that admin user account

@dguyen commented on GitHub (Mar 18, 2025): You should be able to do this through the admin panel which lets you find a document and "reseal" it. To access the admin panel, you need to update a user account to have the "ADMIN" role. You'll need to do this by connecting to the database and editing the user role manually. From then, you can access the admin panel in the top right menu using that admin user account

kerem commented

2026-02-26 18:47:16 +03:00

Author

Owner

@ASchmidt84 commented on GitHub (Mar 18, 2025):

@dguyen Thank you. That helps.
I have one document that is not able to reseal it. How I can figure out the problem?

@ASchmidt84 commented on GitHub (Mar 18, 2025): @dguyen Thank you. That helps. I have one document that is not able to reseal it. How I can figure out the problem?

kerem commented

2026-02-26 18:47:16 +03:00

Author

Owner

@dguyen commented on GitHub (Mar 18, 2025):

You should be able to look in the docker logs to see the error if it happens during resealing

@dguyen commented on GitHub (Mar 18, 2025): You should be able to look in the docker logs to see the error if it happens during resealing

kerem commented

2026-02-26 18:47:16 +03:00

Author

Owner

@ASchmidt84 commented on GitHub (Mar 18, 2025):

no that is not the problem. the button reseal is deactivated on this document

@ASchmidt84 commented on GitHub (Mar 18, 2025): no that is not the problem. the button reseal is deactivated on this document

kerem commented

2026-02-26 18:47:16 +03:00

Author

Owner

@dguyen commented on GitHub (Mar 18, 2025):

For the reseal button to be enabled, all recipients must have signed the document

This is the button logic

  disabled={document.recipients.some(
    (recipient) =>
      recipient.signingStatus !== SigningStatus.SIGNED &&
      recipient.signingStatus !== SigningStatus.REJECTED,
  )

@dguyen commented on GitHub (Mar 18, 2025): For the reseal button to be enabled, all recipients must have signed the document This is the button logic ``` disabled={document.recipients.some( (recipient) => recipient.signingStatus !== SigningStatus.SIGNED && recipient.signingStatus !== SigningStatus.REJECTED, ) ```

kerem commented

2026-02-26 18:47:16 +03:00

Author

Owner

@ASchmidt84 commented on GitHub (Mar 18, 2025):

Okay. Thank you. I will check this.

@ASchmidt84 commented on GitHub (Mar 18, 2025): Okay. Thank you. I will check this.

kerem referenced this issue

2026-02-26 19:31:25 +03:00

[PR #488] [MERGED] feat: require old password for password reset #1005

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#488

No description provided.

Rows
Columns