> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/debugging-and-testing/aurena-debugging/ifs-debug-console.md). # IFS debug console In Aurena there's two debug options. The log window and the debug console. This section will cover the debug console. The log window doesn't add any value to the OData debugging. The information we are looking for is easier to find in the debug console and Inspect console in Chrome. To open the debug console; press your name in the upper right corner in Aurena. Then choose **Debug** and **Enable debug console**.

Maybe you are familiar with the "System info" console in EE, the debug console is the Aurena equivalent. In this console we will have a look at the **Server invokes** and **Page info** tabs. ### Page info Page info offers info about the current page (and child pages elements/entities) you display in Aurena. Information consists of **LU Name, Entity** and **Projection** info. Projection name and Entity is useful when adding projections to the Novacura OData connector which is covered in the [Broken mention](broken://pages/MzQ7dBfCqMjNTvLb69jt) section.

### Server invokes In the Server invokes tab the HTTP OData calls are logged. Chrome Inspect console offers better functionally to inspect Request, Requests details, Payload and Reponses but in the Server Invokes it's possible to navigate direclty to the **API Explorer** which is an important page for exploring OData projections. Additionally the translated OData queries can be view as SQL statements.

--- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.novacura.com/flow-ifs-cloud-development-guidelines/flow-development-with-odata/debugging-and-testing/aurena-debugging/ifs-debug-console.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.