> 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/archive-an-inactive-record.md). # Archive an inactive record Remove finished or obsolete work from active views while keeping its history and references. Podigee Audio Video Ad Server lets you archive a finished or obsolete record without deleting its history. After the first mention, this article uses Podigee Ad Server for the product name. Use this task when an item no longer belongs in active work, but its decisions, references, and evidence must remain available. Archiving is not a replacement for deleting a mistake. If the record is a duplicate, first confirm which record is authoritative. If a new version must take its place, prepare that replacement before you archive the old record. ## Before you start * You have permission to manage the selected record. * You know why the record is no longer active. * You have checked whether current Campaigns, inventory, integrations, or other records depend on it. * You know whether the archive should happen now or at a planned time. * You know the active replacement, if the record has one. Do not archive a record to hide a delivery, billing, privacy, or security problem. Resolve or document that problem first. ## Open the archive task 1. Open **Monetization > Revenue jobs**. 2. Select **Lifecycle and identity**. 3. Select **Archive an item**. ![The current One Podigee Revenue jobs page guides operators to a job before they change a record.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-0cf33f037b414e6d8ee7a4b1eeb843c73115bd0a%2Fdoc-monetization-068-revenue-jobs.png?alt=media) *Open the guided job that matches the result you need. Podigee runs the required checks behind the job.* ## Choose the record and reason 1. In **Item to archive**, select the exact record. 2. Check the record name, type, current state, and latest saved version. 3. In **Archive reason**, select the reason that best describes the change: * **No longer in active use** * **Duplicate item** * **Replaced by a newer item** * **Commercial relationship ended** * **Test or training item** 4. In **Replacement item**, select the active successor when one exists. Select **No replacement** when there is no successor. 5. In **Archive from**, choose now or a future time. Use the exact reason. The reason helps other operators understand why the item left active work and becomes part of the record history. ## Review the dependency check Podigee checks current dependencies before it archives the record. Review the result and stop if it shows an active Campaign, booking, delivery route, integration, or other record that still needs the item. If a dependency must continue to use the same business fact, select a valid replacement or update the dependent record first. Do not bypass a blocking dependency by choosing a different archive reason. ## Apply the archive 1. Check the record, archive reason, replacement, archive time, and dependency result. 2. Confirm that you reviewed the exact item. 3. Select **Archive item**. 4. Wait for the result page. The action is bound to the selected record version. If another operator changes the record while the form is open, Podigee stops the action instead of archiving the newer state. ## Confirm the result Check that: * The record state is **Archived**, or **Scheduled** when you selected a future time. * The record no longer appears in normal active-work lists. * Its history, evidence, and old references remain available to permitted users. * The reason, archive time, and replacement are visible in the result. * Existing work that must continue has a valid active replacement. Archiving does not change an already recorded delivery or financial result. It changes whether the record is offered for new active work. ## If Podigee blocks the action * **The item is already archived:** Stop. Open its history and confirm that you selected the right record. * **A dependency blocks the archive:** Keep the item active until the dependent Campaign, booking, route, or integration has a safe replacement or an explicit end boundary. * **The saved version changed:** Open the task again and review the current version. * **The archive time is invalid:** Select a valid current or future time. * **The exact record is missing:** Refresh the task and check the workspace and scope before trying again. * **A replacement is required:** Select an active replacement that has the authority and state needed for the dependent work. ## Expected result The selected record is removed from active work at the chosen boundary, while its history and evidence remain available. No active delivery or commercial commitment is silently disconnected. ## Next useful tasks Use [Update an Inventory package safely](/documentation/grow-and-monetize/monetization/update-an-inventory-package-safely.md) when the record needs a governed successor instead of an archive. Use [Reconstruct and export audit evidence](/documentation/grow-and-monetize/monetization/reconstruct-and-export-audit-evidence.md) when you need to show who archived the record, which version was used, and why. --- # 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/archive-an-inactive-record.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.