# Common Issues

## Visibility/Sizing issues

\
In some parts of the application, you might encounter this screen:

<figure><img src="https://2125458392-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F7ZtGORbo72v8xjXMpLDs%2Fuploads%2FK2cJR0ao6MCcPg2qOw4G%2Fterminal-too-small.png?alt=media&#x26;token=e68f5e59-9358-44ed-ab32-a22205ae6967" alt=""><figcaption></figcaption></figure>

This can occur for many reasons:

* Terminal window is not large enough.
* The display resolution of your device is smaller than the supported  1920x189 resolution.
* Scaling and or other display issues.

Quick fixes:

* always run Zaun in full screen.
* reduce the scaling factor in your device settings.
* use a device that has a minimum display resolution of 1920x1080.&#x20;

## Missing or Malformed files

If you see errors about missing files or de-serialization issues, here are steps you can take to resolve them:

* Firstly pinpoint the file with the issue
* Make sure the format is as expected by the program by re-extracting from your application version's zip file.
* If not, replace the malformed file with your newly extracted file and copy your configuration values to it.
* If the file is missing, or accidentally deleted, then simply extract a new one and place it in the appropriate directory.

## Bundle Confirmation Issues

If you find that your bundles simply don't want to land. here are some of the probable causes:

* Spamming operations. The Bundle Guard account may sometimes lag behind if operations are done in a fast and successive manner, such as quickly funding then cleaning then funding etc..
* Insufficient balance, Sometimes its simply that the bundle itself just fails regardless, such as the case of not having enough funds to pay tip or transaction fees.
* Network Or RPC Issues: Sometimes the network/RPC can be the bottleneck and lead to bundles not confirming
* TLS/Websocket issues, Web sockets are used internally by the application to confirm transaction landing on chain. if they are misconfigured not working, it will lead to bundle timeouts excluding the fact of the bundle actually landing or not,


---

# Agent Instructions: 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:

```
GET https://zaun.gitbook.io/zaun-usage-manual/common-issues.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.