> 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/manage-an-operational-issue.md). # Manage an operational issue Take ownership of a delivery issue, diagnose it, apply a safe response, and close it after recovery. Use **Operations** when delivery needs attention. An operational issue keeps the impact, owner, diagnosis, safe response, recovery evidence, and completion record in one place. Do not resolve an issue only because you applied a response. First confirm that clean podcast delivery is working. ## Before you start You need access to Monetization and permission to manage delivery issues. Select the correct Monetization workspace before you make a change. The exact actions depend on the issue state. If another operator owns the issue, contact that operator before you change the response. ## Find the issue Open **Monetization > Operations**. ![The current One Podigee Operations page shows one high-impact delivery issue, current incidents, recovery work, and delayed evidence receipts.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-6db53133b0902c0ebe2d348da5710f6f8cfe7c7b%2Fdoc-monetization-067-operations.png?alt=media) *Start with the item that has the highest listener or revenue impact.* Use the page totals to identify urgent work. Then open the exact issue. The issue page shows the impact, current owner, state, and time of the latest evidence. ![A current One Podigee delivery issue shows high impact, no owner, a detected state, and the latest evidence time.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-f7b6f811b54f142e009fe8e87a79c69ff1cb765a%2Fdoc-monetization-067-issue-detected.png?alt=media) *Read the impact and response rule before you take ownership.* ## Take ownership Select **Take ownership**. The issue now has one accountable operator, and its response timing is active. If you cannot take ownership, check the required role or response rule. Do not continue under another person's authority. ## Record the diagnosis Select the cause that best matches the available evidence. Add a short diagnosis that explains: * what changed; * what delivery or revenue is affected; * what evidence supports the cause; * whether clean source media is still available. ![The current One Podigee issue workflow asks for a controlled cause and an evidence-based diagnosis.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-a9f80eb5fedcde86fd0a404472823fb142391397%2Fdoc-monetization-067-diagnosis-form.png?alt=media) *Use the controlled cause for reporting. Use the note to explain the evidence in plain language.* Do not choose a cause only to move the workflow forward. If the evidence is incomplete, keep the issue open and investigate the related Campaign, decision, media, or delivery evidence. ## Prepare the safe response When Podigee has a safe response, select **Prepare safe response**. This step prepares the exact change. It does not change live delivery. Review the response and its effect. A common safe response pauses new paid decisions while clean podcast delivery continues. Existing valid playback can remain available. If no safe response is available, the issue page explains what is missing. For example, the workspace can need an active delivery publication. Fix the missing requirement or use the partner support route when an external provider owns the next action. ## Apply the response Select **Apply safe response**. Read the confirmation, then select **Apply safe response** again. ![The One Podigee confirmation explains that new paid decisions will pause while clean podcast delivery remains available.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-2cc8e19df6ec3ed26d22498a37a399c5f393a7b8%2Fdoc-monetization-067-apply-confirmation.png?alt=media) *Confirm only after you understand the listener and revenue effect.* After the change, the issue moves to **Monitoring recovery**. Paid decisions can remain paused while Podigee checks clean delivery. ![The current One Podigee issue shows Monitoring recovery and confirms that paid decisions are paused while clean podcast delivery stays available.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-e07201e99e1b030a0b64e37c86d2a0d2b3540eee%2Fdoc-monetization-067-monitoring.png?alt=media) *The response protects listeners first. It does not prove that recovery is complete.* ## Verify recovery Select **Check clean delivery** after the delivery response has had time to take effect. Podigee checks the active delivery state and records the recovery evidence. If the serving network has not confirmed clean delivery, the issue stays open. Wait for the current response to finish, review the delivery evidence, and check again. ![The current One Podigee issue stays in Monitoring recovery when clean podcast delivery is not yet confirmed.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-951f7ad6a7455ad00876c169f377857ed0fe259a%2Fdoc-monetization-067-recovery-pending.png?alt=media) *A failed recovery check does not close the issue or hide the unresolved delivery state.* ## Resolve the issue When clean delivery is confirmed, review the recorded recovery evidence. Add a completion note, then select **Resolve issue**. The completion note should state what recovered and what follow-up remains. A resolved issue can still leave paid delivery paused. Review the delivery state and resume monetization separately when it is safe and authorized. ## Escalate a partner issue Use **Partner support** only when a connected delivery or demand partner owns the next action. The action is available only when Podigee has a verified partner operations route and a current evidence package. Send the minimum evidence that the partner needs. Keep one accountable owner in Podigee and track the partner response from the issue. ## Expected result The issue has an accountable owner, an evidence-based diagnosis, an authorized response, and a verified recovery record. Listener delivery is protected, unresolved recovery cannot be hidden, and any return to paid delivery is a separate deliberate action. --- # 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/manage-an-operational-issue.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.