Skip to content

[bug] video ref async tasks fail immediately after a successful dry-run #184

Description

@xccyes-cyber

[bug] video ref async tasks fail immediately after a successful dry-run

Environment

  • CLI: bl 1.18.1
  • Skill: bailian-protocol / bailian-gen 1.18.1
  • Node: v24.18.0
  • OS: macOS 14.8.7 (23J520)
  • Region: cn-beijing (account and endpoint redacted)

Reproduce

bl video ref --async --output json \
  --model wan3.0-video \
  --image ~/path/to/shot05.png \
  --image ~/path/to/shot07.png \
  --image-voice ~/path/to/music.wav \
  --resolution 1080P --ratio 9:16 --duration 15 --watermark false \
  --prompt "[redacted: image-1 to image-2 music-synchronised studio performance]"

The same request with --dry-run --output json succeeds and returns a valid payload containing two reference_image media objects and one reference_audio media object.

Expected

The asynchronous request should enter queue/processing, or return a structured validation, quota, content, or service error explaining why it cannot run.

Actual

The submission returns a task ID, then the task is marked FAILED about two to three seconds later. bl video task get --output json --verbose returns HTTP 200 and only the task status/timestamps, without an error code, reason, hint, or failure detail.

Evidence

Task ID Result Submit / end Request ID from verbose task query
42e2da41-ab3d-463a-9fc1-b1b23336ee6b FAILED 2026-09-01 12:14:19 → 12:14:21 99a1470e-d9cb-9b06-8e95-37bee72b3fc0
a86a9582-5844-4793-a2a7-3e98848c016b FAILED 2026-09-01 12:32:55 → 12:32:57 not captured
2c12812c-e47d-4f26-96d7-5c028def31fb FAILED 2026-09-01 12:47:37 → 12:47:39 5c544fac-4335-9bec-8aa0-e2745b10feca

The account was reported recharged before the last two submissions; the symptom remained unchanged. bl auth status was healthy. No CLI/skill version mismatch was present. Search for open duplicates with gh issue list --repo modelstudioai/cli --search "video ref task FAILED dry-run" --state open --limit 10 returned no results.

Frequency

Always for this request path in this environment (three consecutive paid async submissions following a successful dry-run).

Requested investigation

Please expose the provider-side failure reason through bl video task get, or clarify whether this wan3.0-video reference-to-video configuration has an account/region-side restriction that is not surfaced in the task response.

Activity

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