Local Reducer Policy for Handling Conflicting Video Job Status Updates
A Seedance client may receive asynchronous video job observations out of order, and naive overwrites could let an old running status erase a completed result. The article presents a local reconciliation reducer that allows queued, running, succeeded, and failed states, preventing terminal states from moving backward. When contradictory terminal observations arrive, the reducer retains the first terminal label and flags a conflict requiring UI reconciliation. The author stresses this is a local display policy, not a provider status specification, and that it cannot determine which conflicting response is authoritative. Tests cover progress, duplicates, conflicts and unknown values, but do not prove exactly-once execution or remote job outcomes.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in