> 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/resolve-an-unsafe-creative-or-quarantined-asset.md). # Resolve an unsafe creative or quarantined asset Review a quarantined audio or video creative and release, retain, or destroy it safely. Podigee Audio Video Ad Server places an audio or video creative in quarantine when a media check, external address, provider response, or other safety check needs a decision. After the first mention, this article uses Podigee Ad Server for the product name. A quarantined creative is not ready for Campaign assignment or delivery. Use this task when the quarantine has enough evidence for an operator to decide what happens next. If the issue is an active credential or security incident, use the security incident workflow first and keep the creative in quarantine. ## Before you start * You have permission to decide quarantined creative work. * The creative is still in **Quarantined** state. * You know why the creative was quarantined. * You have checked the master, relevant renditions, and any provider or external-address result. * You know whether the creative can be scanned again, must remain held, or must be destroyed. * You know the retention date when the decision is **Keep in quarantine**. Do not open, download, assign, or publish a quarantined creative through another path to bypass the safety decision. ## Open the quarantine decision job 1. Open **Monetization > Revenue jobs**. 2. Select **Security, privacy, and audit**. 3. Select **Decide a quarantined creative**. 4. Choose the exact audio or video creative from **Quarantined creative**. The list contains only creative versions with a current quarantined media preparation. Check the creative family and version against the incident, media check, or provider notice before you continue. ## Review the evidence 1. Check the master file and every available rendition. 2. Check the security scan result and preparation state. 3. Check the quarantine reason. 4. Check any external address or provider response that caused the hold. 5. Check whether the current subject version is still the one under review. The decision is bound to the exact creative version and its subject digest. If a new version was uploaded, decide the new version separately. Do not use an earlier clean result for a changed file. ![The current One Podigee Creative page shows a clean security scan, ready format preparation, one rendition, the master asset, and Creative coverage.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-1163f404bbc5126ba88f9402f165480b0f51469d%2Fdoc-monetization-045-media-checks.jpg?alt=media) *Use Media checks to confirm that the master is clean and at least one rendition is ready.* ## Choose the decision Select one result: * **Release for preparation:** use this when the evidence supports another preparation scan. The creative moves to scanning. It is not ready for delivery until preparation completes. * **Keep in quarantine:** use this when the issue is not resolved or more evidence is needed. Set **Keep until** to the approved retention date. * **Destroy the quarantined media:** use this when the media must not remain available. The system verifies the destruction receipt before it records the result. Select the governed **Quarantine reason** that explains the decision. Do not use a general reason to hide a provider, safety, rights, or format problem. ## Review and apply the decision 1. Check the creative family, creative version, subject digest, decision, reason, and retention date when applicable. 2. Confirm that the media is still quarantined. 3. Select **Apply action**. 4. Wait for the operation result. The operation locks and checks the creative again before it changes the state. If another operator changed the creative, the decision stops without changing the newer state. ## Confirm the result Check the result page: * **Release:** preparation state is **Scanning**. Wait for the next media result before assignment. * **Keep:** preparation state remains **Quarantined**, with the reason and retention date recorded. * **Destroy:** preparation state is **Failed**, and the verified destruction receipt is recorded. Keep the decision receipt with the related Campaign, Creative, or operational issue. Do not tell a buyer or publisher that the creative is ready until the preparation state and coverage both show a usable result. ## If the decision cannot be completed * **The creative is no longer quarantined:** stop and inspect the newer preparation result. * **The subject version changed:** review the current version and its new evidence. * **The reason is not available:** do not select a similar reason. Ask the safety or security owner to register the correct reason. * **Destruction evidence is invalid:** keep the creative held and report the storage problem. Do not mark the media as destroyed. * **The provider or external address remains unsafe:** keep the creative in quarantine and follow the related incident or connector recovery process. * **The decision needs more time:** choose **Keep in quarantine**, set a clear retention date, and assign the next review. ## Expected result The exact quarantined creative has one governed decision and one signed result. It is either sent back to preparation, retained with a clear review boundary, or destroyed with verified evidence. No unsafe or unverified media enters Campaign delivery. ## Next useful tasks Use [Understand media checks and prepared renditions](/documentation/grow-and-monetize/monetization/understand-media-checks-and-prepared-renditions.md) to interpret preparation states. Use [Manage an operational issue](/documentation/grow-and-monetize/monetization/manage-an-operational-issue.md) when the quarantine is part of a wider delivery problem. --- # 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/resolve-an-unsafe-creative-or-quarantined-asset.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.