> 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/app/en/using-the-app/sign-logs.md).

# Sign logs

Get complete visibility over your Sign logs and syncs with Salesforce from L'App Gonexa.

{% hint style="info" %}
**Prerequisites**

* You have already created an App account
* You are a Gonexa Sign customer
* You have connected your environment in the App
  {% endhint %}

## View Sign logs

This dedicated section gives you access to the complete history of logs related to signature requests, with detailed tracking and status.

* **Real-time log monitoring**: view all signature requests
* **Status of each log**: quickly identify those in **success** or in **error**
* **Simplified retries:** in case of an error, you can manually restart the synchronization with Salesforce
* **Time savings:** no need to contact support to handle a desynchronization; everything is now at your fingertips.

## Review Sign logs

To review and retry Sign logs, follow these steps:

* Log in to L'App Gonexa
* Go to the "**Sign**" tab, then "**Logs**"
* Choose the desired environment (previously connected to the App)
* A list of logs is displayed, filtered on the last 24 hours
* Use the available filters to refine your search by status, date, etc.
* If an error is detected, click the relevant log, then click the "**Retry this log**" button to restart the synchronization with Salesforce

{% hint style="warning" %}
**Tip**

*Remember to refresh the list after a retry to check that the status has been updated.*
{% endhint %}

![List of Sign logs in the App](https://content.gitbook.com/content/MXHiWjspBVPRVSdBvi50/blobs/aUl89aH0YlRwWW8knFRx/app-13.png)


---

# 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/app/en/using-the-app/sign-logs.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.