starred/documenso

Fork 0

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

[GH-ISSUE #2215] Envelope status remains PENDING after all recipients have signed #639

New issue

Closed

opened 2026-02-26 18:47:52 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @Minifab on GitHub (Nov 19, 2025).
Original GitHub issue: https://github.com/documenso/documenso/issues/2215

Bug Description

When all recipients complete signing a document, the envelope status remains
PENDING instead of automatically updating to COMPLETED.

Steps to Reproduce

Create a new document with 2 recipients
Send the document for signing
Both recipients sign the document successfully
Check the document status in the Documents list

Expected Behavior

After all recipients have signed, the envelope status should automatically change to
COMPLETED.

Actual Behavior

The envelope status remains PENDING with the message "Waiting for others to sign"
even though:

All recipients show signingStatus: SIGNED in the database
All recipients have a valid signedAt timestamp

Database Evidence

-- Envelope status
SELECT id, status FROM "Envelope" WHERE id = 'envelope_xxx';
-- Result: status = 'PENDING'

-- Recipients status
SELECT email, "signingStatus", "signedAt" FROM "Recipient" WHERE "envelopeId" =  'envelope_xxx';
-- Result: Both recipients show SIGNED with valid timestamps

Workaround
i tried to but the signed file is not signed. 
Manually updating the envelope status in the database:
UPDATE "Envelope" SET status = 'COMPLETED', "completedAt" = NOW() WHERE id =  'envelope_xxx';

Environment

- Documenso Version: v2.0.0 (Docker image from Nov 18, 2025)
- Deployment: Self-hosted via Coolify
- Database: PostgreSQL 17

Additional Context

The internal jobs system is configured with:
- NEXT_PRIVATE_INTERNAL_WEBAPP_URL=http://localhost:3000

It's possible the job responsible for finalizing the envelope after all signatures is not executing properly.

Originally created by @Minifab on GitHub (Nov 19, 2025). Original GitHub issue: https://github.com/documenso/documenso/issues/2215 ## Bug Description When all recipients complete signing a document, the envelope status remains `PENDING` instead of automatically updating to `COMPLETED`. ## Steps to Reproduce 1. Create a new document with 2 recipients 2. Send the document for signing 3. Both recipients sign the document successfully 4. Check the document status in the Documents list ## Expected Behavior After all recipients have signed, the envelope status should automatically change to `COMPLETED`. ## Actual Behavior The envelope status remains `PENDING` with the message "Waiting for others to sign" even though: - All recipients show `signingStatus: SIGNED` in the database - All recipients have a valid `signedAt` timestamp ## Database Evidence ```sql -- Envelope status SELECT id, status FROM "Envelope" WHERE id = 'envelope_xxx'; -- Result: status = 'PENDING' -- Recipients status SELECT email, "signingStatus", "signedAt" FROM "Recipient" WHERE "envelopeId" = 'envelope_xxx'; -- Result: Both recipients show SIGNED with valid timestamps Workaround i tried to but the signed file is not signed. Manually updating the envelope status in the database: UPDATE "Envelope" SET status = 'COMPLETED', "completedAt" = NOW() WHERE id = 'envelope_xxx'; Environment - Documenso Version: v2.0.0 (Docker image from Nov 18, 2025) - Deployment: Self-hosted via Coolify - Database: PostgreSQL 17 Additional Context The internal jobs system is configured with: - NEXT_PRIVATE_INTERNAL_WEBAPP_URL=http://localhost:3000 It's possible the job responsible for finalizing the envelope after all signatures is not executing properly.

kerem

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

closed this issue
added the
status: triage
label

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Nov 19, 2025):

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 (Nov 19, 2025): 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:47:53 +03:00

Author

Owner

@Minifab commented on GitHub (Nov 19, 2025):

Update - Solution Found ✅

I was able to resolve this issue on my self-hosted instance (v2.0.0 via Coolify).

Root Cause

The background jobs were stuck in PENDING status because the job provider wasn't configured. The jobs were being created but never executed.

Solution

Add these environment variables to your Docker Compose / deployment:

- NEXT_PRIVATE_JOBS_PROVIDER=local
- NEXT_PRIVATE_INTERNAL_WEBAPP_URL=http://localhost:3000


1. After adding these variables, you need to redeploy (not just restart)
2. Old jobs created before the fix will remain stuck - they need to be deleted manually:
DELETE FROM "BackgroundJob" WHERE status = 'PENDING';
3. New documents will work correctly with jobs processed immediately

@Minifab commented on GitHub (Nov 19, 2025): ## Update - Solution Found ✅ I was able to resolve this issue on my self-hosted instance (v2.0.0 via Coolify). ### Root Cause The background jobs were stuck in `PENDING` status because the job provider wasn't configured. The jobs were being created but never executed. ### Solution Add these environment variables to your Docker Compose / deployment: ```yaml - NEXT_PRIVATE_JOBS_PROVIDER=local - NEXT_PRIVATE_INTERNAL_WEBAPP_URL=http://localhost:3000 1. After adding these variables, you need to redeploy (not just restart) 2. Old jobs created before the fix will remain stuck - they need to be deleted manually: DELETE FROM "BackgroundJob" WHERE status = 'PENDING'; 3. New documents will work correctly with jobs processed immediately

kerem referenced this issue

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

[PR #639] [MERGED] feat: Refactor OG Image Generation #1094

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

No description provided.

Rows
Columns