Skip to content

Troubleshooting

Problems senders and admins actually run into, with the fix for each. If your problem is with generating a document rather than signing one, see Troubleshooting in the reference section.

Send is refused with a banner about a missing setting. The banner names the setting and where to fill it in. Once it is filled in, your draft is still there, ready to send. See One-time org setup.

The org-wide email address is verified, but the check still fails. The address must be allowed for all profiles. Open it in Setup and change it from selected profiles to Allow All Profiles.

The send screen warns that the PDF already has a digital signature. Signing removes the old digital signature, and the signed copy carries the new signatures instead. An earlier signer’s marks may still show on the page. You can still send.

Settings will not save a Signature mode. Tiers 1 to 4 must be set up for your organisation before you can choose them. The message names the mode. See Signing tiers.

The signer got the invitation but no verification code. Your org needs a verified Org-Wide Email Address that is allowed for all profiles. Choose it as the E-sign from address in Settings.

A signer says they are waiting for something that never arrived. Check the request on the Sliick Signatures card on the record. If an email could not be sent, the card shows Stalled - something was not delivered, names the signer, and says what to do. The request stays open and the signer can still sign. The next reminder will reach them.

A signer sees “Too many attempts”. Choose Reset signer verification on the request. They can then ask for a new code.

In a request signed in order, the next signer has not been invited. The next signer is invited only when every signer before them has signed. To chase the signers who have not signed yet, use Resend reminder on the request. A CC recipient never holds up the order.

Reminders are on but nothing is going out. The user who saved the reminder schedule may have been deactivated or lost access. Any admin can fix it by saving the reminder schedule again. See Settings.

The signing page loads but no document appears. Turn on guest access to files and records for the site in Experience Workspaces.

Signers see an “under construction” page. The site must be both published and activated.

Changes have not appeared after an upgrade. Republish the Experience site, then ask the signer to reload the page. Do this straight after every upgrade so signers always see the latest page.

The signing page shows “eSignature” and mentions an invitation email. This is normal when the page is opened without a signing link, for example in Experience Builder. If you see it while testing with a real link, check that the component’s Signing token (leave empty) property is empty.

Everyone signed, but nobody has received the final PDF. You are emailed, and the request shows Assembly pending. Choose Finalize signed copies on the request to try again. If that still does not work, you are offered a certificate-only package, which sends recipients the signed document and the Certificate of Completion. If you do nothing, that package is sent automatically after seven days.

A signer cannot download their signed copy. Signers must enter their verification code before they can download. If you reset their verification after the request completed, they are asked to verify again and can then download.

The Certificate of Completion shows no location for a signer. The signing site was not republished after an upgrade. Republish it, and locations are recorded from then on. Requests already signed keep a blank location. See After every upgrade.

The request says “Sealing failed - retry”. Choose Retry sealing on the Sliick Signatures card. If it keeps failing, tell us and we will fix it.

If the card says a retry will not help, follow the steps it shows: replace the document (Duplicate & resend, then Change document) or contact Sliick support.

A deployment is refused because a scheduled job is pending. Clear the reminder schedule, deploy, then set it again. Or, in Setup under Deployment Settings, allow deployments while jobs are pending.