check_job
Read-onlyIdempotent
Check the status/result of a job previously returned by generate_image, generate_video, generate_video_from_image, or generate_video_with_reference.
Besides status/result it reports PROGRESS, so you can tell the person something
truthful instead of "still waiting":
queue_position — how many jobs are ahead (1 = next to be picked up); only while queued
queue_seconds — how long it sat in the queue
run_seconds — how long the generation itself has been running
account_used — which Google account it ran on, once finished
while running, also:
elapsed_s — seconds since the worker picked it up
attempt / accounts_total — which of the owner's Google accounts is being tried
(attempt > 1 means earlier accounts failed and it rotated on)
phase — submitting | voice_synth | polling (polling = Google accepted it and
it is rendering; that is the normal wait)
last_error — why the previous account's attempt failed (emails masked)
hint — the same thing in one human sentence
A job that is queued behind others needs patience; one that has been running far longer
than its model's typical time (see list_models) is the one worth reporting as stuck.
Rotation has a ceiling: a video stops trying new accounts after ~10 min (images and voice
after ~3 min), and stops early when the same error repeats on 3 accounts in a row — the
job then fails with that error and the number of accounts tried, so tell the person the
reason instead of retrying the identical request.
Once status is 'done', SAVE THE FILES: the response carries `download_urls` (no auth
header needed) and `save_as` (filenames). Write them into the user's project — e.g.
./media/<save_as> — and tell them where. The URLs expire within the hour, and the
server's own copy can be reclaimed when its disk fills; the copy in their project is
the one that lasts.Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| job_id | Yes | ||
| include_preview | No |