starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 05:46:01 +03:00

[GH-ISSUE #1222] [Bug] Draft record not visible in documents until page load #343

New issue

Closed

opened 2026-02-26 18:46:36 +03:00 by kerem · 5 comments

kerem commented

2026-02-26 18:46:36 +03:00

Owner

Originally created by @vaishak10 on GitHub (Jul 5, 2024).
Original GitHub issue: https://github.com/documenso/documenso/issues/1222

Issue Description

Description

Hey there,
When tried to duplicate the document with confirmed status, a preview of the document shows with the duplicate and cancel buttons. When you click on the duplicate button the user is taken to document edit page where a notification pops up saying that the document has been duplicated successfully.
Now the catch is, If I route back to the documents page the duplicate document which should be in draft status is not appearing in the documents table. Only after the page reload the draft document appears in the documents table.

Environment: Production - https://app.documenso.com

Preview

https://github.com/documenso/documenso/assets/52874416/95835686-9bd5-4ec8-b384-b4d7cd2273be

Steps to Reproduce

Steps to Reproduce the issue

Open the application and navigate to a document with confirmed status. In the document preview, confirm that there are options to duplicate and cancel.
Click on the "Duplicate" button in the document preview interface. You should be redirected to the document edit page.
On the document edit page, observe the notification confirming that the document has been duplicated successfully.
Navigate back to the main documents page where the table listing documents is displayed.
Verify that the duplicated document, which should be in draft status, is not immediately visible in the documents table.
Refresh or reload the documents page.
After reloading, verify that the duplicated document now appears correctly in the documents table under draft status.

Expected Behavior

If the user navigates away from the document edit page back to the documents list, the duplicated document should already be visible in the table under draft status.
This ensures consistency in the application's UI and provides immediate feedback to the user that the duplication was successful.

Current Behavior

The duplicated document only becomes visible in the documents table after the user manually reloads or refreshes the page.

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

MacOS

Browser [e.g., Chrome, Firefox]

Brave, FireFox

Version [e.g., 2.0.1]

1.67.123(brave); Firefox/127.0

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 @vaishak10 on GitHub (Jul 5, 2024). Original GitHub issue: https://github.com/documenso/documenso/issues/1222 ### Issue Description ### Description Hey there, When tried to duplicate the document with confirmed status, a preview of the document shows with the duplicate and cancel buttons. When you click on the duplicate button the user is taken to document edit page where a notification pops up saying that the document has been duplicated successfully. Now the catch is, If I route back to the documents page the duplicate document which should be in draft status is not appearing in the documents table. Only after the page reload the draft document appears in the documents table. Environment: Production - https://app.documenso.com ### Preview https://github.com/documenso/documenso/assets/52874416/95835686-9bd5-4ec8-b384-b4d7cd2273be ### Steps to Reproduce ### Steps to Reproduce the issue 1. Open the application and navigate to a document with confirmed status. In the document preview, confirm that there are options to duplicate and cancel. 2. Click on the "Duplicate" button in the document preview interface. You should be redirected to the document edit page. 3. On the document edit page, observe the notification confirming that the document has been duplicated successfully. 4. Navigate back to the main documents page where the table listing documents is displayed. 5. Verify that the duplicated document, which should be in draft status, is not immediately visible in the documents table. 6. Refresh or reload the documents page. 7. After reloading, verify that the duplicated document now appears correctly in the documents table under draft status. ### Expected Behavior If the user navigates away from the document edit page back to the documents list, the duplicated document should already be visible in the table under draft status. This ensures consistency in the application's UI and provides immediate feedback to the user that the duplication was successful. ### Current Behavior The duplicated document only becomes visible in the documents table after the user manually reloads or refreshes the page. ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] MacOS ### Browser [e.g., Chrome, Firefox] Brave, FireFox ### Version [e.g., 2.0.1] 1.67.123(brave); Firefox/127.0 ### 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. - [ ] I have included any relevant screenshots. - [ ] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [X] I want to work on creating a PR for this issue if approved

kerem

2026-02-26 18:46:36 +03:00

closed this issue
added the
Stale

status: triage
labels

kerem commented

2026-02-26 18:46:37 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jul 5, 2024):

Thank you for opening your first issue and for being a part of the open signing revolution!

One of our team members will review it and get back to you as soon as it possible 💚

Meanwhile, please feel free to hop into our community in Discord

@github-actions[bot] commented on GitHub (Jul 5, 2024): Thank you for opening your first issue and for being a part of the open signing revolution! <br /> One of our team members will review it and get back to you as soon as it possible 💚 <br /> Meanwhile, please feel free to hop into our community in [Discord](https://documen.so/discord)

kerem commented

2026-02-26 18:46:37 +03:00

Author

Owner

@vaishak10 commented on GitHub (Jul 5, 2024):

To the maintainers, I can work on this!

@vaishak10 commented on GitHub (Jul 5, 2024): To the maintainers, I can work on this!

kerem commented

2026-02-26 18:46:37 +03:00

Author

Owner

@emmpaz commented on GitHub (Jul 10, 2024):

Hey! This is a similar I worked on in issue #1192. If you want to take a look at that and see if that can help fix this.

@emmpaz commented on GitHub (Jul 10, 2024): Hey! This is a similar I worked on in issue #1192. If you want to take a look at that and see if that can help fix this.

kerem commented

2026-02-26 18:46:37 +03:00

Author

Owner

@vaishak10 commented on GitHub (Jul 11, 2024):

Hey! This is a similar I worked on in issue #1192. If you want to take a look at that and see if that can help fix this.

Sure, Will take a look into the solution. Thanks

@vaishak10 commented on GitHub (Jul 11, 2024): > Hey! This is a similar I worked on in issue #1192. If you want to take a look at that and see if that can help fix this. Sure, Will take a look into the solution. Thanks

kerem commented

2026-02-26 18:46:37 +03:00

Author

Owner

@ephraimduncan commented on GitHub (Aug 23, 2025):

This is currently fixed in the latest version.

@ephraimduncan commented on GitHub (Aug 23, 2025): This is currently fixed in the latest version.

kerem referenced this issue

2026-02-26 19:30:56 +03:00

[PR #343] [MERGED] feat: added custom not-found or 404 pages #895

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

No description provided.

Rows
Columns