03 Poll Artifact Until Completed

Step 3: Poll until completed

From here the fast path is identical to the on-demand path โ€” the auto-created artifact walks the same lifecycle. Re-send GET /artifacts/{{af_artifact_id}} until status is succeeded (failed / cancelled are the other terminal states).

What this step does & why it's needed

Same gate as the on-demand poll step: it confirms the artifact has finished generating before you try to download. Two async stages sit behind the fast path โ€” the upload processing (Step 2) and the artifact generation (here) โ€” so reaching a completed ingestion task is not the same as having a downloadable bundle. Wait for the artifact's own status: "succeeded", and read error_code on failed to know whether a retry is worthwhile.

Note the row_counts reflect only this upload โ€” the fast-path scope is assets.task_id, so the bundle contains precisely the locations you just uploaded and nothing else.

See the on-demand poll step for the full terminal-state table and the succeeded vs completed naming note.

Next Step

โ†’ Step 4: Mint Signed URLs.