> ## Documentation Index
> Fetch the complete documentation index at: https://developers.apob.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Tasks and results

> Track asynchronous generation and distinguish acceptance, completion, failure, and downloadable outputs.

Generation runs asynchronously. A successful submission means that work has been
accepted; the final media may still be processing.

## Follow the existing task

A submission receipt identifies the operation. Save the task identifier and any
content identifier returned with it.

| Resource | Meaning |
| - | - |
| Task | The operation whose progress and outcome you follow. |
| Content | The generation that groups related media outputs. |
| Media | An individual image, video, or audio result. |

Model creation has a separate task and readiness check. Use the model's status
flow for training and the generation's result flow for media creation.

## Interpret the outcome

| Outcome | Next action |
| - | - |
| Accepted or processing | Continue checking the existing task with a bounded polling interval. |
| Finished successfully | Retrieve and inspect the final media. |
| Failed or blocked | Review the reported outcome and relevant input, account, or moderation issue. |
| Submission outcome uncertain | Reconcile account history before considering another submission. |

A terminal outcome means the task has stopped running. It does not necessarily
mean that it succeeded. Do not infer success from an identifier, elapsed time,
or an intermediate progress value.

## Retrieve your outputs

The MCP generation result flow returns eligible final outputs after the generation
finishes. Private results are restricted to their owner. Use the top-level task
returned by submission rather than an internal processing task.

Output links can expire. Retrieve the same result again to obtain fresh links;
an expired download link does not require a new generation. Download the files
you need and inspect their dimensions, duration, and content before using them.
Watermark behavior can depend on the account and output.

## Keep reads separate from writes

Reading an existing generation's status does not submit another generation or
consume generation credits. A repeated creation call starts a separate operation
and can consume credits again.

Use the [generation workflow](/guides/generation-workflow) for the full sequence,
or [troubleshooting](/troubleshooting) when the outcome is unclear.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.