> For the complete documentation index, see [llms.txt](https://university.gonexa.fr/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://university.gonexa.fr/university/en/error-codes/gnx1301.md).

# GNX1301 – The recipient does not receive the signature request email

Error code 1301 (GNX1301). When a document is sent for signature, the signature request and the recipient are created in Salesforce but no signature request email is sent.

**Error code:** `GNX1301`

## Error description

When a document is sent for signature, the signature request and the recipient are created in Salesforce but no email is sent to the recipient.

## Solutions

Here are a few things to check:

* An email template ID is entered in the Sign custom setting
* An email template ID is entered in the document template
* An email template ID is entered in the signature request flow, in the "Create certified delivery" action
* Activities are allowed on the object used for the signature request, and the Email button is added to the page
* Email bounced on the contact: the contact's email address is either invalid, or a tool is blocking email delivery
* Email deliverability is set to "All email"
* The user's profile has access to the Org-Wide Address
* The email template used is accessible to the user


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://university.gonexa.fr/university/en/error-codes/gnx1301.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.