> 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/understand-safe-failure-and-preserved-state.md). # Understand safe failure and preserved state Understand what stays safe after a failed action and choose a controlled retry or recovery. Podigee protects the last confirmed state when an action fails or its result is uncertain. A failed upload, forecast, review, publication, provider call, report, or money action does not automatically replace the current live version. Use this guide before you retry. First identify what the system confirmed. Then decide whether to retry the same request, prepare a new version, or open an operational issue. ## Read the visible state Open the operation or record and note: * The action name. * The current state. * The affected workspace, show, Campaign, or report. * The saved version and effective time. * The last confirmed delivery or commercial state. * The error message and time. * Any retry, resume, rollback, or escalation action. Common states have different meanings: * **Queued** means the request is saved and waits for background work. * **Running** means work is in progress. Do not start a second request from another page. * **Blocked** means a required check or decision is missing. Correct that reason first. * **Failed and retryable** means the request did not complete and the displayed retry is safe. * **Failed and terminal** means the request needs a new version, a new input, or an owner. * **Completed** means the result and its receipt are available. Check the result before you act again. ## What remains unchanged When an action fails, Podigee keeps the last confirmed state for the affected scope. Depending on the action, this can include: * The current published Campaign or Delivery version. * The existing RSS feed and episode identity. * A creative that was already approved and live. * A reservation that was already confirmed. * A report definition and its completed runs. * Delivery, analytics, invoice, and payout evidence already recorded. ![The current One Podigee Launch readiness page shows an Active delivery state with controls to pause new ad decisions, roll back, or revoke the Campaign.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-0f74b77e5b511a108476ac120aa6b75354fe2d85%2Fdoc-monetization-061-live-delivery-active.png?alt=media) *The displayed state is the last state that Podigee confirmed with the delivery system.* A failed candidate can remain visible for review without becoming listener-facing. A failed request does not count as a delivered ad, invoice line, or payout unless the relevant evidence confirms it. ## Choose a safe next action ### Retry the same request Retry only when the operation shows a retryable failure or the page provides a retry for the exact same request. Confirm the workspace, scope, version, and input have not changed. Use this path for a temporary background or provider problem when the displayed action is still valid. Do not change the form while you retry. ### Prepare a new version Prepare a new version when the input is stale, the rights window changed, the media changed, the forecast changed, or the current version is no longer the correct business decision. Keep the old version unchanged until the new version passes its checks. Use [Upload an audio or video master](/documentation/grow-and-monetize/monetization/upload-an-audio-or-video-master.md), [Compare forecast scenarios](/documentation/grow-and-monetize/monetization/compare-forecast-scenarios.md), or [Amend Campaign terms or schedule](/documentation/grow-and-monetize/monetization/amend-campaign-terms-or-schedule.md) for a new version. ### Pause or return delivery Use [Pause or resume paid delivery](/documentation/grow-and-monetize/monetization/pause-or-resume-paid-delivery.md) when new paid decisions must stop but current playback must remain safe. Use [Roll back a migration](/documentation/grow-and-monetize/monetization/roll-back-a-migration.md) when a delivery migration is not safe to keep live. ### Open an operational issue Use [Manage an operational issue](/documentation/grow-and-monetize/monetization/manage-an-operational-issue.md) when the error affects live delivery, a paid promise, a provider, or money evidence and the smallest correction is not clear. Preserve the operation, request, and evidence references in the case. ## Do not repeat an uncertain action Do not start a second action when: * The first request is still **Running** or **Queued**. * The browser closed before the result appeared. * A provider may have accepted the request but did not return a receipt. * A report or money action has an unknown external result. * A live delivery change has no confirmed boundary. Open the original operation and refresh it. If the result remains unknown, ask the operation owner to check the receipt and evidence before any retry. ## Check the result after a retry After a retry or new version: 1. Confirm the operation is **Completed**. 2. Confirm the saved version and effective time. 3. Confirm the intended delivery state. 4. Check one representative audio or video request when delivery is affected. 5. Check analytics and commercial evidence for one countable result. 6. Close the issue only when the evidence agrees. For reports, also check the report period, scope, data-as-of time, and output destination. For providers, check the provider receipt and the safe response. For money actions, check the invoice, settlement, or payout receipt. ## If the state looks wrong * **The new version is live unexpectedly:** pause new paid decisions and open an operational issue. * **The old version is not visible:** check lifecycle and version history before creating another. * **The same result appears twice:** stop retries and preserve both operation receipts for reconciliation. * **Delivery and money evidence disagree:** stop the affected commercial action and use [Reconcile sources that do not agree](/documentation/grow-and-monetize/monetization/reconcile-sources-that-do-not-agree.md). * **A provider result is unknown:** do not send the request again until the provider boundary is checked. ## Expected result You know which state is still confirmed, which request failed, and which next action is safe. The current live version and evidence remain protected while you retry, prepare a new version, pause delivery, or 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/understand-safe-failure-and-preserved-state.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.