> 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-review-or-launch-readiness-blocker.md).

# Fix a review or Launch readiness blocker

Find the exact review or Launch readiness blocker, correct the smallest dependency, and prepare the current Campaign setup again.

Use this guide when an approval is missing, a review was returned or rejected, a review expired, or Launch readiness does not allow publication. The page names the exact dependency. Follow that path instead of changing several parts of the Campaign at the same time.

## Identify the blocker

Open **Monetization**, then open the Campaign and **Launch readiness**. Read the first blocked area and its **Next action**.

Launch readiness checks these areas:

| Area                      | What must be current                                     | Typical blocker                                                          |
| ------------------------- | -------------------------------------------------------- | ------------------------------------------------------------------------ |
| Commercial approval       | The current Campaign terms have the required decision.   | Terms changed or approval is missing.                                    |
| Inventory and reservation | Every Flight has eligible Inventory and enough capacity. | Inventory is missing, stale, or not reserved.                            |
| Creative coverage         | Every Flight has a valid audio or video Creative.        | The Creative is not ready, rights are narrow, or coverage is incomplete. |
| Campaign setup            | All connected records belong to one prepared version.    | A Flight, break, policy, or delivery setting changed.                    |
| Launch checks             | The current setup passed the required checks.            | Checks failed, were not run, or need refresh.                            |
| Publication review        | The configured review rule is satisfied.                 | A reviewer is required, or an approval expired.                          |

![The current One Podigee Launch readiness page shows a blocked Inventory connection, a clear repair action, and an earlier passed setup that is no longer valid for publication.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-bb208a14199e200f3bef18aadaa9d1f5a1dd235f%2Fdoc-monetization-052-inventory-blocker.jpg?alt=media)

*Use the displayed Next action. An earlier passed setup does not clear a current blocker.*

## Check the review rule first

The workspace can use different rules for different action families:

* **No approval required:** The authorized operator can continue.
* **Optional review:** Another person can advise, but the review does not block the action.
* **Solo confirmation:** The authorized operator confirms the exact action.
* **Independent review:** A different authorized person must approve it.

Read the rule on the current request. Do not ask for a second reviewer when the workspace does not require one, and do not bypass an independent review when the rule requires it.

## Fix a missing approval

1. Open **Approvals**.
2. Filter by **Pending** and the relevant item type.
3. Open the request for the current Campaign setup.
4. Confirm the item version, request context, rule, required decisions, and expiry.
5. Ask the authorized reviewer to decide, or confirm it yourself when the displayed rule permits.
6. Return to Launch readiness and refresh the checklist.

![The current One Podigee Approvals page shows approved Campaign setup and ad break placement requests with filters, item versions, required decisions, and expiry dates.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-518cfa89c3e153c05b164839d192ee2a4643cde0%2Fdoc-monetization-053-approvals-list.jpg?alt=media)

*Filter by state and item type to find the request for the current setup.*

An approval for an older Campaign version does not approve a newer version. Open the request and compare its short reference and version fingerprint with the setup shown in Launch readiness.

## Fix a returned or rejected review

Read the reviewer's reason and the section that needs attention. Then choose the smallest repair:

| Review result            | What it means                                                  | Correct action                                                                              |
| ------------------------ | -------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
| **Returned for changes** | The work can continue after a named correction.                | Correct that section, create the new exact version, and request review again when required. |
| **Rejected**             | The proposed version must not proceed.                         | Create a suitable new version. Do not edit the rejected evidence.                           |
| **Canceled**             | The request no longer authorizes the item.                     | Create a new request when the work still needs review.                                      |
| **Expired**              | The request passed its expiry time without a current decision. | Confirm the item is still current and request a new review.                                 |

Do not mark a returned or rejected request as complete with a comment. The corrected Campaign, Creative, break, or policy needs its own current decision.

## Fix a changed setup

Launch readiness shows **Refresh needed** when a connected record changed after the last check. This can happen after a Campaign term, Flight, break, Inventory package, Creative assignment, right, policy, or delivery setting changes.

1. Open the named connected record.
2. Confirm the change is intentional.
3. Save the current record version.
4. Return to the Campaign.
5. Run the exact Campaign checks again.
6. Complete the review rule shown for the new setup.
7. Return to Launch readiness.

Do not publish while the page shows a refresh requirement. The earlier passed result is evidence of the earlier setup only.

## Fix a launch check failure

Open the failed check details. The message should identify the affected area, such as Inventory, Creative coverage, ad breaks, destination support, or a provider connection.

Use this order:

1. Correct the named input.
2. Confirm that the record is ready and belongs to the current Campaign version.
3. Run the exact Campaign checks again.
4. Complete a new review when the changed setup requires it.
5. Return to Launch readiness.

Do not correct unrelated warnings before the first blocking dependency is clear. This keeps the operator on the shortest safe path.

## Confirm that publication can continue

Continue only when all six areas show current ready results. Confirm that:

* The commercial approval refers to the current Campaign version.
* Inventory and capacity are current for every Flight.
* Creative media, rights, and coverage are complete.
* The prepared setup includes the intended breaks and delivery methods.
* Launch checks passed after the last change.
* The review rule is satisfied, or the page allows solo confirmation.

![The current One Podigee Launch readiness page shows every required area ready, the publication confirmation, the active earlier delivery setup, and the exact prepared Campaign setup.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-b084c1e94404e4a34193ece7fb0c51ef0c5e4fbb%2Fdoc-monetization-054-ready-to-publish.png?alt=media)

*A ready checklist is the point at which publication can be considered.*

Launch readiness does not publish the Campaign. Use the separate publication action and confirm the exact setup again before it goes live.

## If the blocker remains after a correct repair

Refresh the page and check whether a new version or a new blocker was created. Do not retry a review or publication request repeatedly when the visible version has changed.

Escalate when the same current version remains blocked after one correct repair, when the page shows conflicting versions, or when a destination has no clear reason. Include the short Campaign and review references, the visible state, the named blocker, and the time of the last check.

## Expected result

The operator knows why the Campaign cannot continue, corrects the smallest dependency, and has a current review and Launch readiness result for the exact setup. A missing review, stale check, or older approval cannot accidentally authorize a changed Campaign.


---

# 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-review-or-launch-readiness-blocker.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.