Skip to content

Scene indexing stays stuck in processing at 0% across multiple videos #105

Description

@hjh3700-commits

Summary

index_scenes() starts successfully, but the scene index remains in processing with progress 0 indefinitely. I reproduced this on two different YouTube videos. Other VideoDB functionality works normally in the same environment.

Environment

  • macOS 26.6.2
  • Claude Code 2.1.251
  • ECC 2.2.0
  • VideoDB Python SDK: videodb 0.6.1 (installed successfully)

What works

  • API connection / get_collection()
  • YouTube upload ✅
  • Spoken-word / transcript indexing ✅
  • Dialogue search ✅
  • Search results return playable timestamps ✅

Example verified dialogue results included:

  • elephants → approximately 2.84s–3.52s
  • cool → approximately 5.2s / 13.6s

What fails

Scene indexing only:

  1. Upload a YouTube video.
  2. Call index_scenes().
  3. A scene_index_id is returned.
  4. Poll the index status repeatedly.
  5. Status remains processing, progress remains 0.
  6. Scene search cannot run because the index never reaches a completed state.

This reproduced on two different videos, including a short public test video.

Observed identifiers from the reproductions:

  • First stuck scene_index_id: e8baf44a1965fe31
  • Second test video id: m-z-01a051cb-8676-77d3-b8f6-ba5d6c203b0c
  • Second stuck scene_index_id: a48d89af2e372e38

The second test was polled 30 times over ~15 minutes and remained processing with progress 0 for the entire period.

Retry / cleanup attempts

  • Retried status polling for an extended period.
  • Tried deleting the stuck scene index; the delete request returned a server-side error.
  • Tried recreating scene indexing; the API reported an existing scene index already in processing.
  • Repeated the full test with a different video; dialogue indexing completed in seconds, while scene indexing again stayed at processing / 0.

Why this looks server-side

The same API key, SDK installation, connection, upload pipeline, transcript indexing, dialogue search, and timestamp retrieval all work correctly. Only scene indexing fails, and it fails identically across two separate videos. This makes a client configuration or API-key problem unlikely.

Expected behavior

Scene indexing should eventually transition from processing to a completed state so that scene search can be executed.

Actual behavior

Scene indexing remains processing at progress 0 indefinitely, preventing scene search.

No API keys or secrets are included in this report.

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