> 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/concepts-and-reference/state-and-version-reference.md). # State and version reference Read the common Monetization states and understand which changes need permission, review, a new version, or a safe recovery action. States describe where a record or operation is in its current lifecycle. A state is not a promise that delivery, analytics, or money work is complete. Always read the state together with its reason, version, and next action. ## Common record states | State | Meaning | What you can do | | ------------------ | ------------------------------------------------------------------ | ---------------------------------------------------- | | **Draft** | A saved version is not active. | Edit it, test it, or submit it for review. | | **Pending review** | A decision is waiting for the configured review rule. | Review or request the required decision. | | **Returned** | A reviewer asked for a named correction. | Create a corrected version and request review again. | | **Rejected** | The version must not proceed. | Create a suitable new version. | | **Approved** | The exact version passed its review. | Continue to readiness or publication. | | **Ready** | Required checks for the next operation passed. | Perform the next action shown on the page. | | **Blocked** | A named dependency prevents the next operation. | Follow the displayed repair path. | | **Expired** | A time boundary ended before the state could continue. | Create or request a current version. | | **Archived** | The record is kept for history and is not selectable for new work. | Use a current successor when available. | ## Delivery states ![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 delivery state is the last state confirmed with the delivery system.* | State | Meaning for new requests | | --------------------- | -------------------------------------------------------------------------- | | **Scheduled** | The current confirmed setup stays in control until the effective time. | | **Resuming** | The previous confirmed state stays in control while the resume is checked. | | **Active** | Eligible requests can use the verified setup. | | **Paused** | New paid decisions stop and the configured fallback applies. | | **Replaced** | A newer verified setup controls new requests. | | **Revoked** | New paid decisions stop permanently for this publication. | | **Activation failed** | The last confirmed setup remains in control. | **Rolled back** describes an action. The previous healthy setup becomes active, and the replaced setup remains visible as history. ## Operation states | State | Meaning | Safe operator response | | ------------------------ | ------------------------------------------------------ | ---------------------------------------------- | | **Queued** | Work is waiting to start. | Wait or use the displayed action. | | **Running** | Work is being processed. | Do not submit a duplicate operation. | | **Waiting for evidence** | A player, provider, or destination result is expected. | Check the stated source and boundary. | | **Retryable failure** | A temporary dependency failed. | Repair the dependency and retry once. | | **Terminal failure** | The operation cannot complete without a new input. | Correct the input and create the next version. | | **Completed** | The operation has a durable result. | Read the result and evidence. | ## Integration states | State | Meaning | | ----------------------- | ---------------------------------------------------------------------- | | **Configured** | The connection values are saved but not yet certified or active. | | **Testing** | A managed or provider test is running. | | **Certified** | The declared capability passed the required evidence checks. | | **Active** | The connection can be used for its allowed scope. | | **Suspended** | New use is stopped while the connection remains for history or repair. | | **Rejected** | The provider or review rejected the version. | | **Provider-controlled** | The destination controls final processing or playback. | Do not confuse a connected state with a delivered result. A provider can be active while one request returns no-fill or an invalid response. ## Finance states | State | Meaning | | ------------- | --------------------------------------------------------------------- | | **Prepared** | A Settlement period or draft money record exists. | | **Approved** | The exact invoice, payout, or period passed its review. | | **Issued** | An invoice was issued and has a document identity. | | **Submitted** | A payout or accounting record was sent to its destination. | | **Paid** | The payout destination confirmed payment. | | **Held** | A named finance or compliance hold prevents progression. | | **Closed** | The Settlement period is locked. Later changes require an adjustment. | An invoice or payout state does not change delivery evidence. A closed period does not accept a silent edit. ## When a new version is required Create or use a new version when a change can affect: * commercial terms, dates, quantity, rate, currency, or targeting; * Flight media, destination, or delivery goal; * Inventory, ad break, capacity, or reservation; * Creative master, rendition, rights, review, or coverage; * delivery setup, provider capability, or fallback; * metric, tax, currency, or finance rules; * report scope, metrics, schema, or recipient. A comment on an old version does not turn it into the new version. The new version must pass the checks and review that its action family requires. ## State transitions and authority | Transition | Usually needs | | -------------------------------- | ------------------------------------------------------------------ | | Draft to review | Edit permission and a complete version. | | Review to approved | The configured review rule. | | Approved to ready | Current checks and connected records. | | Ready to active | Publication permission and delivery confirmation. | | Active to paused | Delivery-control permission and a pause reason. | | Paused to active | Repair, current checks, and resume confirmation. | | Active to replaced | A verified replacement and publication confirmation. | | Active to revoked | Delivery-control permission and permanent withdrawal confirmation. | | Open to closed Settlement period | Complete invoices, payouts, reconciliation, and close review. | Your workspace can make review optional or allow a solo confirmation. The state page shows the rule for the exact action. Do not assume that another object uses the same rule. ## Read version identity The interface shows short, copyable references for records and versions. Use them to compare pages and support packages. Copy the full identifier only when support or an integration owner asks for it. Before you approve, publish, retry, or reconcile, compare: * record name and type; * short version reference; * current state and reason; * effective period; * connected source versions; * review and check result. If a version changed while the form was open, refresh and review the current version again. ## Expected result You can explain what each state means, what new work is allowed, and which change requires a new version or review. Operators do not treat a pending, approved, forecast, or provider state as proof that delivery or money is complete. --- # 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/concepts-and-reference/state-and-version-reference.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.