Runway HTTP and Task Failure Triage

Overview

Runway has two failure planes: synchronous HTTP responses and asynchronous task terminal states. Triage must preserve the task ID, selected model schema, and redacted evidence before deciding whether a retry is safe.

Prerequisites

• Task ID or redacted HTTP response with request correlation
• Model, endpoint, API version, SDK version, and request fingerprint
• Access to current HTTP-error and task-failure guidance

Instructions

Step 1: Identify the failure plane

If create returned no task ID, classify the HTTP status. If a task exists, retrieve it and classify THROTTLED, FAILED, CANCELLED, or malformed SUCCEEDED output separately.

Step 2: Protect against duplicates