KOkobaltlabs
reviews

Retry Metadata Task

Changed on

Retry the review's MetadataTask after its ReviewMetadataAgentRun failed.

This intentionally does not create a ReviewMetadataAgentRun itself — dispatch_metadata_run_task (review_reporting_stage_wf) is the only place one is ever created (see the module docstring on backend/tasks/review_reporting_stage.py), which is what guarantees metadata can't start ahead of the reporting it may depend on. This endpoint only clears the failed run's agent_run_id, under the same row lock dispatch_metadata_run_task uses for its own check-then-write, and then re-dispatches the stage workflow so it re-evaluates the review from scratch — which also means a retry picks up any ReviewReportingTask created since the task was last dispatched, not just the metadata agent in isolation. Only retryable once the prior run reached FAILED; a pending or completed run has nothing to retry.

post/reviews/{review_id}/metadata-tasks/retry

Request

  • Base URL
    https://api.kobaltlabs.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.kobaltlabs.com/reviews/{review_id}/metadata-tasks/retry
  • Auth
    none declared

Path parameters

review_idstring uuid required

Response

Successful Response

task_idstring uuid required
instructionsstring required
set_key_datesboolean required
set_vendor_fieldsboolean required
auto_apply_key_datesboolean required
status'pending' | 'completed' required
agent_run_idstring uuid nullable
agent_run_status'pending' | 'running' | 'completed' | 'failed'
thinkingstring nullable
summarystring nullable

Changes

  • 9fe2fb8a3631Revision changes
    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status

    • info

      added the optional property ////// to the response with the status