> 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-the-correct-recovery-path.md). # Find the correct recovery path Start with the symptom, protect live delivery, and choose the smallest safe recovery action. Start with what you can see, not with an internal system name. This guide helps you choose the smallest safe action for a Monetization problem. It also shows when to stop new paid decisions and when to ask an operations or support owner for help. ## First, protect listeners and money Stop and ask for help before you change anything when: * A listener or viewer receives the wrong audio, video, or ad. * The same delivery appears to count twice. * A creative is unsafe, unlicensed, or clearly not the approved asset. * An external provider reports a credential problem or an unexpected data change. * Delivery, analytics, invoice, or payout evidence does not agree. * A live change has no clear owner, scope, or last verified state. Keep the current live state in place while you collect the exact Campaign, show, episode, delivery state, and evidence references. Do not change the RSS feed to solve an ad delivery problem. ![The current One Podigee Revenue jobs page shows guided work such as commercial context, policies, inventory, and editorial ad breaks.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-0cf33f037b414e6d8ee7a4b1eeb843c73115bd0a%2Fdoc-monetization-068-revenue-jobs.png?alt=media) *Choose the job family that describes the result you need.* ## Choose the symptom ### I cannot open Monetization or I see the wrong show Check the workspace and show scope first. Then check your membership and role. Use [Set the workspace and show scope](/documentation/grow-and-monetize/monetization/set-the-workspace-and-show-scope.md) and [Add, change, revoke, or restore user access](/documentation/grow-and-monetize/monetization/add-change-revoke-or-restore-user-access.md). ### The record is not in the list Check the active filters, workspace, show, record type, and lifecycle state. Search for an archived or replaced version before you create a new record. Use [Use Revenue jobs](/documentation/grow-and-monetize/monetization/use-revenue-jobs.md) and [Archive an inactive record](/documentation/grow-and-monetize/monetization/archive-an-inactive-record.md). ### Inventory or an ad break is missing Check the episode rights, source media, delivery capability, and current episode duration. Then reassess supply or update the break binding. Use \[Assess first-party podcast supply] (assess-first-party-podcast-supply.md) and \[Prepare episode ad breaks] (prepare-episode-ad-breaks.md). ### A forecast or reservation does not fit Check the forecast time, selected inventory, delivery goals, and current reservations. Recalculate before you promise more capacity. Use [Compare forecast scenarios](/documentation/grow-and-monetize/monetization/compare-forecast-scenarios.md) and [Reserve and change capacity](/documentation/grow-and-monetize/monetization/reserve-and-change-capacity.md). ### A creative is blocked, unsafe, or not available Open the creative status and read the reason. Check the master, prepared rendition, rights window, media format, and coverage period. Use [Preview and inspect Creative media](/documentation/grow-and-monetize/monetization/preview-and-inspect-creative-media.md) and [Resolve a Creative coverage exception](/documentation/grow-and-monetize/monetization/resolve-a-creative-coverage-exception.md). ### A review or Launch readiness check blocks publication Read the blocking check. Confirm whether review is required in your workspace. Correct the exact Campaign or creative version, then run the check again. Use [Run Launch readiness](/documentation/grow-and-monetize/monetization/run-launch-readiness.md) and [Complete the required reviews](/documentation/grow-and-monetize/monetization/complete-the-required-reviews.md). ### A show or Campaign does not become live Check the last confirmed serving state, the selected version, the effective time, and the failure evidence. Do not retry a changed version from an old page. Use [Enable a Podigee show for dynamic ad delivery](/documentation/grow-and-monetize/monetization/enable-a-show-for-dynamic-ad-delivery.md), \[Understand live delivery states] (understand-live-delivery-states.md), and \[Pause or resume paid delivery] (pause-or-resume-paid-delivery.md). ### A listener receives no ad, the wrong ad, or the wrong media Record the request time, show, episode, media type, and visible result. Check the Campaign decision, break binding, creative coverage, fallback, and delivery evidence in that order. Use [Verify one real audio or video delivery](/documentation/grow-and-monetize/monetization/verify-one-real-audio-or-video-delivery.md) and [Explain an ad decision or no-fill result](/documentation/grow-and-monetize/monetization/explain-an-ad-decision-or-no-fill-result.md). For RSS audio, use \[Understand dynamic ad delivery in RSS audio] (understand-dynamic-ad-delivery-in-rss-audio.md). For HLS audio or video, use [Understand Podigee HLS audio and video delivery](/documentation/grow-and-monetize/monetization/understand-podigee-hls-audio-and-video-delivery.md). ### Apple or Spotify delivery reports a problem Separate the Podigee setup from the platform result. Check the asset, association, submission, processing, capability, and campaign state before you retry. Use [Understand Apple Podcasts video delivery and certification](/documentation/grow-and-monetize/monetization/understand-apple-podcasts-video-delivery-and-certification.md), [Choose a Spotify Direct Sales delivery mode](/documentation/grow-and-monetize/monetization/choose-a-spotify-direct-sales-delivery-mode.md), and [Run a Spotify sponsorship](/documentation/grow-and-monetize/monetization/run-a-spotify-sponsorship.md). ### A VAST, OpenRTB, or CATS provider fails Check the provider status, credentials, capability, timeout, and last safe response. Do not keep retrying an unsafe or looping provider response. Use \[Connect a VAST demand source] (connect-a-vast-demand-source.md), \[Connect an OpenRTB demand source] (connect-an-openrtb-demand-source.md), or \[Configure CATS transport] (configure-cats-transport.md). ### A report, event, or money total is stale Check the report run, source timestamps, event processing state, and reconciliation case. Preserve the original evidence before you retry. Use \[Monitor delivery, pacing, fill, and revenue] (monitor-delivery-pacing-fill-and-revenue.md), \[Reconcile sources that do not agree] (reconcile-sources-that-do-not-agree.md), or \[Manage an operational issue] (manage-an-operational-issue.md). ## When to use the operational issue path Open an operational issue when the symptom affects a live show, a paid promise, a provider, or money evidence and the smallest correction is not clear. Record the affected scope, current live state, exact time, evidence references, and owner. Use [Manage an operational issue](/documentation/grow-and-monetize/monetization/manage-an-operational-issue.md) to assign the case, preserve evidence, choose a safe remedy, and verify recovery. ## What not to do * Do not create a duplicate Campaign, creative, show, or commercial account because a filter hides the original. * Do not edit a published version to repair a historical result. * Do not change the RSS feed for a request-time ad problem. * Do not delete a failed operation, provider response, or delivery event. * Do not report a recovery as complete until delivery, analytics, and commercial evidence agree. ## Expected result You have identified the visible symptom, protected the current live state, and selected one safe next action. The selected article tells you what to check, what to change, how to confirm success, and when to escalate. --- # 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-the-correct-recovery-path.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.