> 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/find-a-missing-record.md). # Find a missing show, Campaign, creative, or other record Find a show, Campaign, creative, or other record before you create a duplicate. Use this guide when a record is not in a list or a selector. The record may be hidden by the current workspace, show, filter, lifecycle state, or version. Check these causes before you create another record. ## Check scope and search first 1. Confirm the workspace and show in the sidebar. 2. Clear the search field. 3. Clear status, media, market, and date filters. 4. Search by the business name and then by the external reference. 5. Check whether the list is sorted by a different column or page. ![The Commercial accounts directory filtered to one advertiser named Cedar and Vale Media.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-80b98e39287809ab24a383a2a79f23794657b876%2Fdoc-monetization-014-commercial-account-directory.png?alt=media) *Search and filter the directory before you create a new account.* Lists use the selected scope. A record in another show or workspace does not appear in the current list, even when the name is the same. ## Check the record type Confirm that you are looking in the correct area: * A show or workspace is not a Campaign. * A Campaign is not a Flight or an Inventory package. * A Creative family is not a Creative master or prepared rendition. * A Commercial account is not a Brand or legal entity. * A published version is not the same as a draft version. Open **Monetization > Revenue jobs** when you are not sure which job owns the record. Use [Use Revenue jobs](/documentation/grow-and-monetize/monetization/use-revenue-jobs.md) to select the job family by result. ## Check lifecycle state Look for a lifecycle filter or an archived view. A record can be: * **Draft:** available for editing, but not available as a published reference. * **Published:** the current version is available for its permitted work. * **Scheduled:** the version becomes effective at a planned time. * **Paused:** the record remains available, but new delivery or paid decisions may stop. * **Archived:** the record is not shown in normal lists. * **Replaced:** a successor version is now the current reference. * **Revoked:** the record cannot be used for new work. Use [Archive an inactive record](/documentation/grow-and-monetize/monetization/archive-an-inactive-record.md) to review archive rules. Use [Restore an archived record as a draft](/documentation/grow-and-monetize/monetization/restore-an-archived-record-as-a-draft.md) when the record must be used as the starting point for a new version. Do not restore an old record to make outdated terms or media live again. ## Check version history Open the record that is closest to the expected name and review its version history. Confirm: * The current version number. * The version state. * The effective time. * The owner and scope. * The successor or replacement reference. * The reason for a return, archive, or revocation. ![Version 3 of Harbor and Pine Audio Availability Review in Draft state beside another published Inventory 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.* A new version does not create a new business identity. Use the current record and its successor history instead of creating a second record with a similar name. ## Check identity mapping If the record came from another system, check the import mapping or external reference. A mapping can point to a different record type, a different workspace, or an older version. Use [Import records and resolve mappings](/documentation/grow-and-monetize/monetization/import-records-and-resolve-mappings.md) to review the mapping before you import again. If two records represent the same Commercial account or Brand, stop and compare their legal identity, external references, and saved versions. Use [Merge duplicate identities](/documentation/grow-and-monetize/monetization/merge-duplicate-identities.md) only after the canonical record and aliases are clear. ## Check permission and visibility You can have permission to read a list but not permission to see a restricted record or version. Confirm that your role covers: * The workspace or show scope. * The record type. * The lifecycle state. * The current operation, such as edit, publish, or archive. If the correct record is visible to an administrator but not to you, use [Fix missing access or the wrong Monetization scope](/documentation/grow-and-monetize/monetization/fix-missing-access-or-wrong-scope.md). Do not ask an administrator to copy the record into your scope just to make it visible. ## If the record still does not appear Record the following and ask a workspace administrator or support owner for help: * Workspace and show name. * Record type and business name. * Search term and filters used. * Expected external reference. * Last known version or effective date. * Your role and selected scope. * The page and time where the record was missing. Do not include credentials or private provider data in the request. ## Expected result You find the existing record, its current version, or the reason it is not available. You avoid a duplicate record and keep the original identity, history, and commercial evidence intact. --- # 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/find-a-missing-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.