- Shipped
- 7 ஆகஸ்ட், 2026 அன்று 6:52 AM UTC
- Author
- Kamo
- Commit
- 56c5e5c
The session always started at "welcome", so a signer following the link in their completion email — or simply reopening the invitation — was walked through the whole flow a second time and only found out at Finish, as an unexplained "we couldn't submit your signature", that the server refuses a second signature. They now land on their receipt, with the executed document to download once every party has signed. Adds the two refusal reasons ESigService can now return: DELEGATED (this party handed the document on) and NOT_YET (a sequential envelope whose earlier party has not signed).