> 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/fix-a-creative-or-coverage-problem.md).

# Fix a Creative or coverage problem

Find and repair a Creative or coverage problem before it can affect a Campaign or delivery.

Use this guide when a Creative is blocked, quarantined, not ready, or cannot cover the Campaign requirement. The safest repair is the smallest change that makes the exact required media, rights, market, delivery method, and time period valid.

Do not assign a different Creative only because it looks similar. The selected Creative must pass the checks for the exact Flight and destination.

## Start with the visible problem

Open **Monetization**, select **Creatives**, and open the affected Creative. Read the status and the named reason before you edit anything.

Use this table to choose the first check:

| What you see                         | First check                          | Safe next action                                                 |
| ------------------------------------ | ------------------------------------ | ---------------------------------------------------------------- |
| **Quarantined** or security blocked  | Security scan result                 | Keep the version out of delivery. Do not retry an unsafe source. |
| **Preparation failed**               | Format and source details            | Check the master, then upload a corrected version.               |
| **Rights missing or expired**        | Rights and usage window              | Add a valid grant or use a Creative with valid rights.           |
| **Coverage needs attention**         | Media, markets, delivery, and period | Resolve the exact coverage decision.                             |
| **Ready, but the Flight is blocked** | Flight and destination requirements  | Open the Flight coverage and resolve the named mismatch.         |
| **Creative rejected**                | Review or suitability decision       | Correct the content or complete the required review.             |

## Check media preparation

Open **Media checks** and **Delivery formats**. A Creative can be visible in the library while its master is still scanning or its rendition is not ready.

![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)

*A ready rendition is required before assignment.*

Confirm all of the following:

* The security scan is clean.
* Preparation is complete.
* The media type matches the Flight, audio or video.
* The duration is within the supported range.
* The required rendition is ready.
* The source and rendition belong to the intended Creative version.

If a check fails, do not change the Campaign to hide the failure. Upload the corrected master as a new Creative version. Keep the original version for its evidence history.

## Check rights and suitability

Open the Creative rights and review sections. Confirm that the grant covers:

* The complete Campaign delivery period.
* Every selected market.
* The intended delivery surfaces, such as RSS audio or HLS video.
* The commercial use of the media.
* Required disclosures, categories, and suitability rules.

If the right expires before the Flight ends, the Creative cannot cover the complete Flight. Use a replacement with a longer valid period or extend the right through the normal rights workflow.

Do not record a longer date without evidence from the rights holder.

## Resolve a coverage gap

When the Creative shows an open coverage decision, select **Resolve coverage**. The window states the exact requirement. Check the media, markets, delivery method, Campaign, and period before you choose a resolution.

![The current One Podigee Creative page shows one audio coverage decision that needs attention and a Resolve coverage action.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-f6edf0c1d62df909f51973fc449d614b3e7263cb%2Fdoc-monetization-049-open-coverage-gap.jpg?alt=media)

*Resolve the exact requirement that is missing.*

Use a fully prepared replacement when one exists:

1. Select **Resolve coverage**.
2. Select **Use a replacement**.
3. Confirm the Campaign and Flight shown by the window.
4. Select a prepared Creative that covers the complete requirement.
5. Complete the review rule shown for the workspace.
6. Select **Apply coverage decision**.

![The current One Podigee Resolve creative coverage window shows the required media, markets, delivery method, Campaign, and replacement Creative.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-ec1427439d24f855c8e8de624f208608e1d82e16%2Fdoc-monetization-049-use-replacement.jpg?alt=media)

*A replacement must cover the full requirement, not only part of it.*

Podigee checks the replacement again when you apply it. A replacement can fail when its rights, markets, media, delivery method, or period are too narrow.

## Use a temporary exception only when accepted

If no replacement is ready and the business accepts a short gap, use a temporary exception. The exception must have a future end time no later than the Campaign end.

1. Select **Resolve coverage**.
2. Select **Use a temporary exception**.
3. Confirm the Campaign and Flight.
4. Set the expiration time.
5. Complete the configured review rule.
6. Select **Apply coverage decision**.

![The current One Podigee Resolve creative coverage window shows a temporary exception with a fixed expiration time.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-576d0eb9962e3ce901bfb0385be29697be3af476%2Fdoc-monetization-049-temporary-exception.jpg?alt=media)

*A temporary exception has a clear and limited boundary.*

Do not use an exception to bypass a malware result, missing usage rights, an unsupported media type, or a required review. The exception controls the coverage decision. It does not make an unsafe or invalid file ready.

## Check the affected Flight

Open the Campaign and inspect every affected Flight. A Creative can cover audio but not video, or one market but not another. It can also cover the current period but not a later extension.

Check:

* Media format and destination.
* Markets and exclusions.
* Start and end time.
* Required delivery method.
* Creative weights and rotation.
* Frequency and separation rules.
* Capacity and reservation state.

If the Flight requirement changed, update the Campaign plan instead of forcing an unsuitable Creative into the old requirement.

## Confirm the repair

After the repair, open the Creative and the Campaign again. Confirm that:

* The named problem is closed.
* The selected Creative version is the intended one.
* The rendition and rights cover the complete Flight.
* Required review is complete, or the workspace rule allows the configured path.
* No other Flight has an open coverage problem.
* Launch readiness can complete without a new blocker.

![The current One Podigee Creative page confirms that the coverage decision was recorded and that live delivery is unchanged until publication.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-7fdb9397dfdc1a2ea8f1c999e231f2b5475abdd0%2Fdoc-monetization-049-resolved-gap.jpg?alt=media)

*A repair is visible before it changes live delivery.*

The repair changes the prepared Campaign state. Live delivery remains on the current published state until the normal test, review, readiness, and publication flow succeeds.

## If the problem returns

A new Campaign version can create a new problem. Common causes are a new market, a longer period, a new delivery method, expired rights, a changed media format, or a replacement that was removed.

Treat the new message as a new exact decision. Do not reuse an old exception without checking its scope and expiration.

## When to escalate

Escalate when:

* The same valid master fails the same check after one corrected retry.
* The rights record is correct but the Creative still shows expired or missing rights.
* The Campaign and Creative show different versions after refresh.
* A required destination is blocked without a named reason.
* The problem could affect an already published Flight or billing evidence.

Include the short Creative, Campaign, and Flight references, the visible status, the named reason, and the time of the last action. Do not send full technical identifiers in a normal support message. Copy the full value only when support asks for it.

## Expected result

The exact Creative problem is repaired, or a bounded and accepted exception is recorded. The affected Campaign can pass its normal readiness checks, and an unsuitable or unsafe Creative never becomes live by accident.


---

# 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/fix-a-creative-or-coverage-problem.md?ask=<question>&goal=<endgoal>
```

`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.