# Troubleshooting Every refusal in SignPlus says what was refused and why, in a sentence meant to be acted on. This page groups them by where you see them. ## Starting a signing | You see | What to do | |---|---| | *SignPlus is not set up for this space yet* | A space or Confluence administrator has to open the SignPlus settings once. See [configure SignPlus](../configure/) | | *Starting a signing needs permission to edit this page* | Ask for edit access, or ask someone who has it to start the signing | | *This page already has an attachment with that name. Choose another name.* | Change **Document name**. Confluence refuses two attachments with the same name | | *This space requires a message to signers*, or *a signing deadline* | Fill in the field under **Show additional settings** | | *This space does not allow…* | The space's settings rule that option out. Remove it, or ask a space administrator | | *The signing deadline must be in the future* | Pick a later due date or time. The time is read in the zone the information icon names | | *Every signing method is turned off in this space* | An administrator has disabled every method under **Disabled signing methods**. At least one has to stay on | | **Not sent for signing**, with a reason | Nothing was sent to anyone. The reason says what to change; then start it again | | *Dokobit could not be reached, so nothing was sent for signing* | A network problem between Atlassian and Dokobit. Try again in a few minutes | ## While a signing runs | You see | What to do | |---|---| | The signed document never appears on the page | SignPlus checks with Dokobit itself every hour, so a lost notice arrives later. If a day passes, open a support request naming the page and the document | | *SignPlus is not allowed to edit this page, so it could not attach the signed document* | Someone restricted the page after the signing started. Let SignPlus edit it again, or ask a space administrator | | A signer says they got no email | Check the address in **View signing details**. Dokobit's email may be in their spam folder | | A group member was not invited | Confluence gives out no email address for that person. The signing said how many were left out when it was sent | | **Page modified during signing** | Someone edited the page after it was sent. Cancel the signing and start a new one if the change matters | ## Signed pages | You see | What it means | |---|---| | **Page signed but modified** | The page was edited after everybody signed. **compare** shows what changed. The signed file still holds what was signed | | The page cannot be edited after signing | The edit lock stays after a completed signing, on purpose. A space administrator removes it under the page's restrictions | | There is no **Delete** in the signing details | Deleting a finished signing is a Confluence administrator's by default. See [deleting signings](../configure/#deleting-signings) | | The signed document has a watermark | The site was in **Test** signing mode. That document has no legal effect: sign it again once the mode is changed | ## Exports | You see | What to do | |---|---| | *PDF not generated* | Try again. If it fails again, open a support request: the reason is in SignPlus's logs, which Oktul can read without seeing your page | | An image is missing and its description is printed instead | SignPlus could not draw it, or ran out of time fetching images. See [what the document contains](../what-prints/#where-a-pdf-cannot-follow-confluence) | | A Jira table shows a notice, or work item keys rather than cards | SignPlus is not connected to Jira. See [connecting Jira](../install/#connecting-jira) | ## Administrators | You see | What to do | |---|---| | *Could not check the token* | Dokobit refused it, or could not be reached. Copy the token again from your Dokobit account | | The settings say SignPlus has no licence | The subscription has lapsed. Signings already out still complete. See [licensing](../install/#licensing-and-what-happens-when-it-lapses) | | A webhook never fires | The address was not approved in Atlassian's dialog, or the receiving rule is not published. See [webhooks](../automation/#webhooks) | --- A problem or a question? Write to [support@oktul.com](mailto:support@oktul.com) or open a request in the [Help Center](https://oktul.atlassian.net/servicedesk/customer/portals). Both reach the same service desk, so either way the request gets a reference and an SLA measuring the response.