> **Source:** https://knowledge.leegality.com/document-execution/integrations/salesforce/troubleshooting
> **Site:** Leegality Knowledge Base — https://knowledge.leegality.com
> **About:** Leegality is a document execution platform covering eSigning, stamps, NeSL, workflows, and REST API integration.
> **Navigation:** Every article on this site has a plain-text version at `<article-url>.txt` (this format). To get an index of all articles with their `.txt` links, read: https://knowledge.leegality.com/llms.txt
> **AI Guide:** For instructions on how to navigate this knowledge base as an AI agent, read: https://knowledge.leegality.com/ai-readable.txt

---
# Troubleshooting

Common issues with the Leegality for Salesforce integration and how to resolve them.

## Credential setup errors

| Error | Resolution |
| --- | --- |
| "Unauthorized endpoint" | Verify the Named Credentials are created with the exact names shown in [Installation & Setup](https://knowledge.leegality.com/document-execution/integrations/salesforce/installation-and-setup#23-create-named-credentials). |
| "No credentials found" | Ensure the **Leegality External Credential Access** permission set is assigned to the user. |
| "Invalid client credentials" | Verify `client_id` and `client_secret` are correctly entered in the External Credential principal — and that sandbox/production values aren't mixed up. |

## `invalid_client` error during authorization

If you encounter an `invalid_client` error while [authorizing](https://knowledge.leegality.com/document-execution/integrations/salesforce/connect-and-authorize), the client secret configured in Salesforce is invalid. Contact Leegality for assistance and request a new client secret for your environment — a **Sandbox client secret** for sandbox, or a **Production client secret** for production.

Once you receive the new client secret, apply it:

1. Go to **Setup**, search for **Translate** in the Quick Find box, and **enable** the Translation feature.
2. Go back to **Setup** and search for **Custom Labels**.
3. Locate the two labels **`sandbox_client_secret`** and **`production_client_secret`**, and open the one matching your environment.
4. Click **New Local Translations (Override)**.
5. In the **Language** dropdown, select **English**.
6. Enter the new secret key from Leegality in the **Translation Text** field.
7. Save the changes.

The correct client secret is now applied for your environment, resolving the error.

## Dates or times look wrong

Document dates, invitation dates, or date filters showing unexpected values are almost always a timezone mismatch. The Leegality API responds in **GMT**, and Salesforce converts it based on three separate settings:

| Setting | What it affects |
| --- | --- |
| Organization timezone | The Apex job that updates document and invitee details |
| Current user's timezone | Invitation Date and date filters on the All Documents page |
| Guest (site) user's timezone | Webhook processing |

**Resolution:** set the timezone to **Indian Standard Time (IST)** in all three places — the organization settings, each Salesforce user, and the public site's guest user. See [Administration](https://knowledge.leegality.com/document-execution/integrations/salesforce/administration#timezone-configuration) for context.

## Workflows missing from Salesforce

- **NESL and unpublished workflows are filtered out by design** — workflows with the NESL invitee signing type, or workflows unpublished in Leegality, won't appear.
- The list is fetched when you visit the **Workflow Management** tab — revisit the tab to fetch the latest workflows from Leegality.
- A maximum of **99 workflows** can be fetched from Leegality.

## Sending fails or the workflow errors out

- Check that no **mandatory field** is left blank — an error message is displayed if one is.
- Keep payloads under the **6 MB limit** — larger payloads cause failures in the workflow process.

## Status updates not arriving

If document statuses aren't updating in Salesforce, verify the [webhook configuration](https://knowledge.leegality.com/document-execution/integrations/salesforce/administration#webhook-configuration) — in particular, that the site's **Guest User** has both the **Leegality Webhook Permission Set** and the **Leegality External Credential Access** permission set assigned.