Jobs & polling

Create, get a taskId, poll on a later turn — and the one status that lies.

Create, then poll on a later turn

Deck and video creation are asynchronous. The create call returns 202 with a taskId almost immediately; the work continues without you.

Poll every 5 seconds (pollIntervalMs: 5000).
A task handle is good for 24 hours (ttlMs: 86400000).
A deck is usually done inside three minutes.

The five statuses

status	meaning	keep polling?
working	In progress.	Yes
input_required	Stopped, waiting for a human. A video paused for script review lands here and carries a resume link. A deck escalated to our team also lands here and carries NO link — there is nothing for you to action; we come back to you.	No — check for a resume link before assuming there is one
completed	Finished. Read the error field before you celebrate.	No
failed	Our infrastructure failed. Nothing was delivered.	No
cancelled	Abandoned or rejected.	No

The counter-intuitive part

Business failures arrive as completed, with an ai.askdeck/error member saying why — out of credits, brief rejected, over the slide cap. Only an infrastructure failure is failed.

So if (status === 'completed') downloadDeck() is wrong, and it is wrong in the way that costs you money: it downloads nothing and reports success.

Correct

if (task.status === "completed") {
  const err = task["ai.askdeck/error"];
  if (err) return handleBusinessFailure(err);   // out of credits, rejected brief, …
  return downloadDeck(task);
}

input_required is not a failure

When a deck escalates to a human, or a video pauses for you to approve its script, the task reports input_required and the envelope carries a URL to resume at. Stop polling and surface that link. An agent that polls an input_required task every five seconds for 24 hours is burning your rate limit on a task that will never move on its own.