> For the complete documentation index, see [llms.txt](https://docs.ebbot.ai/ebbot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/troubleshooting.md).

# Troubleshoot the Easit integration

Start with the workflow, the run, the ticket number and the internal id, the time with timezone, the expected result, and the first node whose actual output differs. Open the run under **Logs → View run details**: every node shows the arguments it was called with and the response it got.

### Find the failing layer

| Symptom                                            | Check                                                                                                                   | Interpretation                                                                                                                                                                                                                                                                                          |
| -------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| The **Field** dropdown in an action is empty       | Base URL, API token, GraphQL permissions, **Module system name**                                                        | The connection cannot read the module's fields. Leave the module name as `Request` unless the administrator gives another one                                                                                                                                                                           |
| Ping succeeds but other actions fail               | GraphQL access and module permissions                                                                                   | [Ping](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions/ping.md) checks only that the Integration API answers                                                                                                   |
| No run starts                                      | Object rule is active and uses the export; URL ends with this connection's id; a test ticket was saved after activation | Creating the trigger does not configure Easit; the administrator sets up the export                                                                                                                                                                                                                     |
| Several runs per ticket                            | Which event fires the object rule; whether workflow writes save the ticket                                              | The rule fires on each save, including the workflow's own writes. See [Avoid self-triggering loops](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/workflow-patterns.md#avoid-self-triggering-loops)                  |
| Get Easit Item returns a contact or another ticket | Item Id mapping                                                                                                         | Item Id is mapped from `item.sequence_id`. Map `item.internal_id`                                                                                                                                                                                                                                       |
| `No matching field found for key …` on a write     | Item Id mapping, then field system name                                                                                 | Usually the wrong item (see above). Otherwise the field does not exist in this module                                                                                                                                                                                                                   |
| `item.description` is null                         | The ticket in Easit, and that the right item was read                                                                   | The field is empty, or a different item was read. `item.text` shows every non-empty field                                                                                                                                                                                                               |
| Write fails for status, category or priority       | Value is the data-source id                                                                                             | Labels are rejected. Look up ids with [List Easit Field Values](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions/list-field-values.md)                                                                          |
| Run shows **Done** but the ticket did not change   | The write's `success` and `error` outputs                                                                               | A failed write does not fail the run. Add a condition on `success`                                                                                                                                                                                                                                      |
| Knowledge suggestion is irrelevant or generic      | The search query actually sent, the prompt, **Sources**                                                                 | The query should contain only ticket text, and the prompt must contain the ticket. See [Suggest a knowledge article](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/workflow-patterns.md#suggest-a-knowledge-article) |
| Later nodes cannot find the LLM `text` output      | Structured output enabled                                                                                               | With structured output, map `structuredOutput` fields instead                                                                                                                                                                                                                                           |
| Send Easit Email succeeds but no email arrives     | The mail rule in Easit, its trigger field, sender policy                                                                | `success` confirms the field writes and the rule trigger, not SMTP delivery                                                                                                                                                                                                                             |
| Record Easit Ticket Message sent no email          | Expected                                                                                                                | This action never sends email. Use [Send Easit Email](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions/send-easit-email.md)                                                                                     |
| Customer replies do not reach the ticket           | Inbound mail import in Easit (Email2GO or equivalent)                                                                   | The integration does not read mailboxes                                                                                                                                                                                                                                                                 |

### Errors returned by actions

Several actions return a declared error object instead of their normal output. Check for it before using the output in a later step.

* **`ItemNotFound` / `TicketNotFound`**: no item with that id or ticket number. Check which id was passed.
* **`FieldNotFound`**: the field system name does not exist in the configured module.
* **`EasitUnavailable`**: Easit could not be reached or refused the request. `endpoint` names the Easit address that was called, `error` the reason, and `hint` the most likely fix:
  * `HTTP_401` or `HTTP_403`: the API token is wrong or lacks GraphQL permission.
  * `HTTP_404`: the Base URL path is wrong.
  * `ConnectError`: the Base URL host cannot be reached.
  * A timeout: Easit did not answer within 30 seconds.

The error objects for each action are listed on its reference page.

### Requests and retries

Each Easit request times out after 30 seconds. The integration does not retry failed requests. This is not a guarantee about the whole workflow: before re-running a failed run, check which writes already completed, so you do not send an email twice or overwrite a field a person has changed since.

The integration sets no request quota of its own. Easit environments can limit API use; confirm limits with the Easit administrator. Field discovery can make several requests; prefer [List Easit Field Values](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions/list-field-values.md) over [List Easit Fields](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/easit-integration-in-automations/actions/list-fields.md) when you already know the field.

### What to send to Ebbot Support

Send the workflow name, the run link, the ticket number and internal id, the time with timezone, expected versus actual behavior, and the inputs and outputs of the first node that went wrong. Include only the ticket content needed to reproduce the problem. Never send the API token.

### After a fix

Repeat the smallest test that shows the intended result, and confirm that the ticket in Easit changed as expected. Record what was changed, published and verified.
