> 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/restore-an-archived-record-as-a-draft.md). # Restore an archived record as a draft Create a new draft from an archived record without changing the archived history. Podigee Audio Video Ad Server can use an archived record as the starting point for new work. After the first mention, this article uses Podigee Ad Server for the product name. Restoration creates a new draft and keeps the archived record unchanged. Use this task when a former Campaign, account, inventory item, or other record may be useful again. The restored draft is not active, approved, or ready for delivery. It needs current ownership, review, and publication before another operator can use it. ## Before you start * You have permission to create lifecycle drafts in the selected workspace. * The source record is archived. * You know why the work is needed again and what must be updated. * You know who should own the new draft, or you will leave it unassigned. * You can complete the review and publication steps after restoration. Do not restore a record to bring old terms, old permissions, old capacity, or old delivery settings back into active use without checking them. The new draft is a starting point, not a release. ## Open the restore task 1. Open **Monetization > Revenue jobs**. 2. Select **Lifecycle and identity**. 3. Select **Restore an archived item**. ## Choose the archived record 1. In **Archived item**, select the record to use as the source. 2. Check its name, type, archived state, and available history. 3. In **Owner of the restored draft**, select an active workspace member when someone should own the new work. Select **Leave the restored draft unassigned** when the team will assign ownership later. Only archived records of the same supported type can be restored. If the source is not archived or the requested new type does not match, stop and choose a valid source. ![A current One Podigee inventory page shows a successor package in Draft state beside a published package.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-ba31ab239cd9d281bb2ecc59a5b90394ecfddbc5%2Fdoc-monetization-024-successor-draft.jpg?alt=media) *A successor draft makes the pending change visible without presenting it as a published offer.* ## Review the new draft boundary Before you submit, confirm that: * The archived source is the exact record you intend to reuse. * The new draft keeps the same supported record type. * The selected owner is an active member with the needed workspace scope, when an owner is set. * Current business terms, markets, media, policies, and delivery settings will be reviewed again. * The archived source must remain unchanged. Podigee binds the action to the selected source version and its lineage. It uses that binding to show which archived information seeded the new draft. ## Restore the draft 1. Check the archived record, record type, owner, and lineage details. 2. Confirm that you reviewed the exact source. 3. Select **Restore as draft**. 4. Wait for the result page. Podigee creates a new record with a new identifier. It does not unarchive or edit the source. ## Update, review, and publish After the result page: 1. Open the new draft. 2. Replace values that are no longer current, including owner, dates, prices, markets, targeting, media, policies, and external references when they apply. 3. Run the checks required for the record type. 4. Send the exact new version for review when the workspace requires it. 5. Publish only after the current authority, content, delivery, and commercial checks pass. Do not use the archived source in a new Campaign or delivery route. Use the new draft after it has the correct state and any required approval. ## Confirm the result The result must show: * **Draft** for the new record. * A new record identifier that differs from the archived source. * A link to the archived source record. * The selected owner, when one was assigned. * A lineage result that identifies the source version used. The archived record remains **Archived**. Its history, evidence, and old references continue to describe the original work. ## If Podigee blocks the action * **The source is not archived:** Stop. Archive it only when the archive rules are satisfied, or choose an already archived source. * **The source version changed:** Open the task again and review the current archived version. * **The record type is not supported:** Choose a source and new draft type that match. * **The owner is unavailable:** Select an active workspace member in the same workspace, or leave the draft unassigned. * **The lineage check fails:** Do not retry with a different digest. Reopen the task and select the archived source again. * **The draft needs current data:** Update the draft before review. Do not publish copied values that are no longer valid. ## Expected result Podigee creates one new, linked draft from the archived record. The source stays archived, no old settings become active by accident, and the new work can follow the normal review and publication path. ## Next useful tasks Use [Update an Inventory package safely](/documentation/grow-and-monetize/monetization/update-an-inventory-package-safely.md) when the restored draft is an inventory package. Use [Complete the required reviews](/documentation/grow-and-monetize/monetization/complete-the-required-reviews.md) before you publish the new version. --- # 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/restore-an-archived-record-as-a-draft.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.