> 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/support-and-reliability-operator-learning-path.md). # Support and reliability operator learning path A guided path for diagnosing delivery symptoms, applying safe recovery, and escalating with evidence. This path starts with a visible business or delivery symptom. It helps a support or reliability operator find the correct recovery job, protect playback, explain the cause, and give another team an evidence package that can be acted on. ![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 or evidence family that matches the problem.* ## Before you start Read [New ad operations team learning path](/documentation/grow-and-monetize/monetization/new-ad-operations-team-learning-path.md) and [Integration and data operator learning path](/documentation/grow-and-monetize/monetization/integration-and-data-operator-learning-path.md). You need read access to the affected workspace, show, Campaign, delivery evidence, and recent events. Keep the listener or viewer report and the time range. ## Start with the symptom ### 1. Check the operating view Use [Understand where to do daily work](/documentation/grow-and-monetize/monetization/understand-where-to-do-daily-work.md). Check whether the problem is no fill, underdelivery, wrong media, stale processing, failed report, finance mismatch, provider error, or playback risk. ### 2. Explain one decision Use [Diagnose underdelivery, no-fill, or wrong delivery](/documentation/grow-and-monetize/monetization/diagnose-underdelivery-no-fill-or-wrong-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). Start with one request, one episode, one delivery surface, and one exact Campaign or Creative version. ![The current One Podigee decision library shows result, delivery method, and privacy filters next to recent audio and video decisions.](https://2032417310-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FbqUKO6lljHGzkEAzliPI%2Fuploads%2Fgit-blob-c7eb99b997ef8bfe2bd793323a7c682391d3ef15%2Fdoc-monetization-073-decisions-overview.png?alt=media) *Use the decision library to move from a delivery signal to one recorded request.* ## Use the safe recovery job ### 3. Fix the named problem Choose the smallest relevant job: * Use [Fix a forecast or capacity conflict](/documentation/grow-and-monetize/monetization/fix-a-forecast-or-capacity-conflict.md) for supply or reservation problems. * Use [Fix a Creative or coverage problem](/documentation/grow-and-monetize/monetization/fix-a-creative-or-coverage-problem.md) for missing, blocked, or incompatible media. * Use [Fix a review or Launch readiness blocker](/documentation/grow-and-monetize/monetization/fix-a-review-or-launch-readiness-blocker.md) for an incomplete review or publication checklist. * Use [Recover a failed serving activation](/documentation/grow-and-monetize/monetization/recover-a-failed-serving-activation.md) for a serving state that did not activate safely. * Use [Recover stale delivery or event processing](/documentation/grow-and-monetize/monetization/recover-stale-delivery-or-event-processing.md) for delayed or missing processing. * Use [Retry failed report delivery](/documentation/grow-and-monetize/monetization/retry-failed-report-delivery.md) for a missing external report. * Use [Repair finance synchronization](/documentation/grow-and-monetize/monetization/repair-finance-synchronization.md) for a money mapping or acknowledgement problem. ### 4. Protect playback during incidents Use [Protect playback during an incident](/documentation/grow-and-monetize/monetization/protect-playback-during-an-incident.md) when a change could affect listeners or viewers. Preserve the last safe serving state, use the configured fallback, and record the incident before you retry or roll back. ## Escalate with evidence Use [Build a support package and escalate a problem](/documentation/grow-and-monetize/monetization/build-a-support-package-and-escalate-a-problem.md). Include the symptom, exact scope, request time, Campaign and Creative versions, decision, no-fill reason, delivery response, event state, provider result, and money effect. Remove raw identity and credentials before you share the package. ## If the cause is unclear * Reproduce the symptom with one request and one exact version. * Compare the decision, delivered media, event, report, and money record. * Do not change targeting, capacity, Creative, or RSS while you are still identifying the cause. * Ask the accountable owner for a version-bound discussion when a decision is needed. * Escalate when the safe fallback is active, evidence is incomplete, or the issue affects more than one workspace or delivery surface. ## Expected result The operator can explain what failed, what remained safe, what action was taken, and what evidence supports the result. Playback remains protected, no duplicate money effect is created, and the next team receives a small, complete package instead of an unstructured log dump. --- # 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/support-and-reliability-operator-learning-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.