Skip to content

AI resource versions cannot be resubmitted after review completion #15620

Closed

Description

@saynoword

Describe the bug

AI resource submit APIs treat every reviewing version as an active review and return idempotently. If the publish pipeline has already produced a terminal APPROVED or REJECTED result while the resource version still remains reviewing, submitting the version again does not recover the lifecycle state or start a new review.

A reviewed version also cannot be submitted for another review. The console does not expose a resubmit action for either case.

This affects the shared lifecycle semantics used by Skill, Prompt, and AgentSpec.

Expected behavior

The submit behavior should be consistent for all three AI resource types:

  • draft: submit for review as usual.
  • reviewed: allow a new review submission.
  • reviewing with an active pipeline or a terminal result marked historical=true: keep the request idempotent because the current review is still in progress.
  • reviewing with a current, non-historical APPROVED or REJECTED result: recover the stale lifecycle state and allow a new review submission.
  • online / offline: continue rejecting submit requests.

The Next and legacy consoles should expose the resubmit action only when the backend can accept it.

Actually behavior

A submit request for any reviewing version returns without changing the state or starting a new pipeline, even when publishPipelineInfo.status is already APPROVED or REJECTED. A reviewed version is rejected as an invalid submit state.

How to Reproduce

  1. Create and submit a Skill version with a publish pipeline enabled.
  2. Let the pipeline finish with REJECTED (or APPROVED) while the stored version status remains reviewing.
  3. Disable the pipeline or otherwise keep the terminal pipeline result on the version.
  4. Call the submit API for the same version again.
  5. Observe that the version remains reviewing and no new review is started.

The same lifecycle issue applies to Prompt and AgentSpec submit flows.

Desktop (please complete the following information):

  • OS: Any
  • Version: current develop
  • Module: ai, console
  • SDK: HTTP Admin/Console API

Additional context

publishPipelineInfo.historical was introduced to preserve compatibility with historical records whose completed review result was retained while the version still had reviewing status. A historical terminal result must therefore remain idempotent; only a current non-historical terminal result should trigger stale-state recovery.

Activity

  1. added a commit that references this issue on Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions