> For the complete documentation index, see [llms.txt](https://docs.podigee.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.podigee.com/documentation/grow-and-monetize/monetization/schedule-report-delivery.md). # Schedule report delivery Schedule a governed report for recurring delivery to a tested destination, then monitor its runs and repair a failed attempt safely. Use scheduled reports in the Podigee Audio Video Ad Server when people need the same trusted result at a regular time. A schedule runs the saved report definition for the previous reporting period, sends the selected file to a tested destination, and keeps the run and delivery evidence together. ## Before you start Create and save the report first. Confirm that its current definition contains the correct scope, metrics, breakdown, time zone, privacy class, and output format. You need report read permission to open the automation page and report management permission to create a schedule. You also need an active delivery destination. A destination can be an API, SFTP location, object storage location, or data warehouse. The destination must pass its connection test before it can be used for scheduled delivery. ## Open scheduled delivery 1. Open **Monetization > Evidence & Money**. 2. Open **Saved reports**. 3. Select the report that you want to deliver. 4. Select **Automate delivery**. The automation page shows the report version used by the schedule, available destinations, current schedules, recipients, and delivery history. If no destination is available, select **Set up a destination** and complete the connection test first. ![The current One Podigee Evidence & Money page shows report automation alongside saved reports, scheduled reports, and delivery state.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-ab157f76d1c3f5f7be3a2d369de4c2995b42dd3b%2Fdoc-monetization-072-reports-overview.png?alt=media) *Use Evidence & Money to find a saved report and monitor its scheduled delivery state.* ## Create a schedule 1. Enter a clear **Schedule name**, or leave it blank to use the report name and frequency. 2. Choose a **Frequency**: every day, weekdays, every Monday, or the first day of each month. 3. Choose the **Delivery time**. The time uses the report time zone shown in the form. 4. Choose an active, tested **Destination**. 5. Choose a **File format** supported by the saved report. 6. Select **Start scheduled delivery**. The schedule uses the report's current saved definition and the previous reporting period for each run. It does not silently change the report scope, metric definition, currency, or privacy class. Give the schedule a name that explains its purpose, such as **Northstar weekly campaign delivery**. ## Add recipients Use **Report recipients** when people must receive the scheduled result. 1. Select the team members who have report access. 2. Select one or more active delivery destinations. 3. Select **Save recipients** or **Update recipients**. The recipient list and destination list are separate. A person can receive a report only when the person has report access, and a destination can be used only while it remains active. If the page shows no eligible team members, check report access for the workspace. If it shows no destinations, configure and test one before changing the recipient list. ## Check schedule state The **Delivery schedules** section shows the schedule name, file format, time zone, state, and next run. Check it after creation and before a high-value reporting cycle. * **Active** means the schedule can create its next run. * **Needs update** means the saved report definition changed after the schedule was created. Review the report and create or update the schedule so it uses the intended version. * A missing next-run time means that the product has not provided a next run yet. Do not treat this as a completed delivery. The Evidence & Money overview also shows active schedules, completed runs, and items that need attention. A scheduled report does not create an ad decision, reserve inventory, or change a Campaign. It only produces and delivers the selected report result. ## Check delivery history Open **Delivery history** on the automation page. Each destination attempt keeps its state, attempt number, and sent time. Use the latest attempt for the current outcome. Earlier failed attempts stay visible so an operator can explain what happened. If an attempt failed and the page offers **Retry delivery**: 1. Confirm that the destination is active and available. 2. Select **Retry delivery**. 3. Confirm the retry in the dialog. 4. Check the new attempt and its final state. The retry sends the same completed report to the same destination. It does not create a new report definition or alter the original attempt. Do not retry when the destination may already have received the file until you have checked the destination and the delivery state. ## Troubleshoot scheduled delivery | Situation | What to check | | --------------------------------------------- | ------------------------------------------------------------------------------------------------------ | | No destination is listed | Configure a destination, run its connection test, and activate it. | | The schedule cannot be created | Check the frequency, delivery time, file format, and destination. | | The schedule shows **Needs update** | Review the current report definition and create a schedule for the intended version. | | No team member can be selected | Grant report access to an active workspace member. | | A delivery failed | Read the delivery reason, check the destination, then use **Retry delivery** only when it is safe. | | The same report appears with different values | Compare the report version, period, time zone, metric definitions, privacy class, and data-as-of time. | ## Expected result You have a recurring schedule that uses a known report definition, a tested destination, and an explicit reporting time zone. The page shows the next run and keeps a durable history of each delivery attempt, including a safe retry path for failures. --- # 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.podigee.com/documentation/grow-and-monetize/monetization/schedule-report-delivery.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.