-
Notifications
You must be signed in to change notification settings - Fork 50
Closed
Description
Problem:
- After asset generation finishes, the frontend records adoption via /aigc/asset-adoption.
- The current request does not exclude failed or incomplete generation tasks (their outputs are discarded anyway).
- The backend validates task status while collecting task results; for such task IDs it returns HTTP 400.
- As a result, asset adoption fails unexpectedly when the payload contains failed/incomplete task IDs.
Expected behavior:
- Asset adoption should only include successfully completed tasks; or the backend should skip failed/incomplete tasks during aggregation instead of returning 400.
Likely cause:
- The frontend submits all task IDs related to the generation session, including tasks that ended up failed/incomplete and whose outputs were discarded.
Fix options (either or both):
- Frontend: when calling /aigc/asset-adoption, filter out failed/incomplete tasks and only submit task IDs that produced valid outputs.
- Backend: when collecting task results, skip failed/incomplete tasks (or treat them as ignorable) to avoid 400; optionally return partial success with a list of skipped task IDs.
Acceptance criteria:
- If a generation session contains failed/incomplete tasks, asset adoption still succeeds (at least for the successful outputs).
- No 400 is returned solely because the payload contains failed/incomplete task IDs.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels