Jobs and results

Generation, media processing, asset ingestion, and workflow execution can outlast a single client request. Some connector tools wait for completion automatically, but you should not assume every successful call contains a finished output.

Read the response before continuing

Check for a completed output, a processing state, an error, and any identifiers. Keep the original response with its teamspace so another call can retrieve the same work.

Use the follow-up that matches the initial response. An asset ID, transcription ID, and task ID identify different resources.

Poll an existing job

Wait between status checks and respect any retry guidance. Stop on a documented success or failure state. Keep passing the same space_id when you make follow-up calls yourself.

Check the existing video generation job. If it is still running, keep its identifiers and report its status. Do not start another generation.

Recover from a timeout

A client timeout does not establish that the server canceled the job. Retrieve the job or created resource before resubmitting. Repeating a generation request can consume more credits; repeating a create request can produce a second item.

If no identifier was returned, inspect relevant recent resources where possible. Report the uncertainty instead of claiming failure or silently recreating the work.

Report a useful result

Return the actual status, saved IDs, and available output links. On failure, include the error and the next action needed. Do not describe a submitted request or a queued execution as completed content.