> For the complete documentation index, see [llms.txt](https://docs.reportandrun.com/manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.reportandrun.com/manual/faq/c160/c164/q535.md).

# Why are there blank spaces between photos and text in my report?

The layout algorithm may be unable to fill the space entirely.

If you believe there is an error, please [contact us](/manual/faq/c169/q575.md) with the following for troubleshooting:

* screenshots showing the issue
* any templates used when creating the report 
* a [sample JREP](/manual/report-and-run/data/export-jrep.md) that reproduces the issue (if possible)

## Related 

* [FAQ: How do I delete a blank page in a PDF report?](/manual/faq/c160/c164/q534.md)
* [FAQ: How do I reorder the photos in a report?](/manual/faq/c150/c153/q454.md)
* [FAQ: What is the maximum number of characters that can be added to a description in a report?](/manual/faq/c160/c166/q549.md)
* [FAQ: My reports aren’t generating or displaying correctly in PDF format – how do I fix it?](/manual/faq/c160/c164/q536.md)
* [FAQ: Can I combine different image layouts within a single report?](/manual/faq/c150/c156/q500.md)


---

# 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://docs.reportandrun.com/manual/faq/c160/c164/q535.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.