> For the complete documentation index, see [llms.txt](https://docs.verygoodsecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verygoodsecurity.com/vault/developer-tools/larky/print-debugging.md).

# Debugging Compute Operations

This page demonstrates how to use the `print()` function for debugging your program flow. Sandbox environments support the `print()` function. While you can type the `print()` function in a live vault's Larky code, since the live environment is a protected environment, the `print()` function will not execute and will be skipped over.

## Print Logging Code Sample

This sample, when loaded onto a sandbox route, prints a statement to the compute logs that you can view in your compute logs.

```python
load("@stdlib//builtins", builtins="builtins")
def process(input, ctx):
    output = str('This is my log')
    print (output)
    return input
```

## Viewing Compute Logs in the Dashboard

You can view the logs in the compute logs tab. From the left-hand navigation in your dashboard, choose "Logs" then choose the Compute tab on the Logs page.

This sample produces a log entry that looks like this.

<figure><img src="/files/GMYtEADKDZqps1gle7Ev" 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 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.verygoodsecurity.com/vault/developer-tools/larky/print-debugging.md?ask=<question>&goal=<endgoal>
```

`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.