When it fires
POST /v1/markets/{id}/disputes was called for a market whose current resolution proposal you have already disputed. Each user may file exactly one dispute per proposal, and concurrent retries resolve to a single dispute.
Why it happens
- Your client retried a filing whose first attempt actually succeeded (for example, the response was lost in flight).
- Two processes using the same account raced to file for the same market.
How to fix
- Treat this as success: your dispute exists, and it holds settlement until the automated review completes. This holds even if your first attempt returned a 503 after recording the dispute; nothing is lost by stopping your retries here.
- Fetch your dispute, including its review outcome (
status,reviewedAt,reviewNote), withGET /v1/markets/{id}/disputes. - A dispute cannot be amended; the original
reasonstands. If you have material new evidence, contact Kash support.