> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/development/integration-engine/get-started/turn-on-diagnostics.md).

# Turn on diagnostics

In the beginning of the life cycle of an integration it is often helpful to turn on diagnostics, which will enable the integration to save variables as well as input and output message to and from the integration.

Note: your integration data may of course contain confidential and sensitive data from your or other's business worth protecting. Use this functionality with great care. If possible mostly in development and test/QA environments with un-sensitive data. Never leave it on for production environments without a distinct purpose, and never without a conscious decision.

On the integration click the tab Diagnostics.

* Track variable changes - if enabled, you will be able to inspect state of variables before and after each step
* Enable inspecting input to integration - if enabled, you will be able to inspect input to the integration, before any transformation
* Enable inspecting output of integration - if enabled, you will be able to inspect output of the integration, after any transformation

<figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FoArxffSoq62UuxMHP2t2%2Fimage.png?alt=media&amp;token=6b4fe117-6d60-42eb-8f2f-01c36b9465ad" alt=""><figcaption></figcaption></figure>


---

# 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://help.novacuraflow.com/development/integration-engine/get-started/turn-on-diagnostics.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.
