> For the complete documentation index, see [llms.txt](https://docs.testfiesta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.testfiesta.com/reports-tab/reports/scheduling-reports.md). # Scheduling Reports
Step 1: Select a Report to schedule On the Reports page, select the Report you wish to schedule from the Table View.

On the Reports page, select the Report you want to schedule and click "Schedule a report" from the menu.

Step 2: Select schedule criteria and confirm On this screen select the schedule criteria including the increments of time to send the Report from (every day, week, month, or custom options), the exact time within those selections, and emailing the report to specific users.\ \ When you are finished click "Schedule"

Fill in the schedule criteria and click "Schedule, on the bottom right.

Now that we understand how to schedule a Report, a good thing to learn is how to filter Reports to find information quickly. Click "Next" to continue. --- # 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.testfiesta.com/reports-tab/reports/scheduling-reports.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.