## TL;DR

Do not treat a 202 as "done".

## Fix

1. Do not treat a 202 as "done".
   Expected: you can confirm this matches your situation.

## When to use

- You are setting up or using this Coda API writes return 202, not 200 feature.
- The symptom matches: check mutation status with the requestId.

## When NOT to use

- Unrelated Coda API writes return 202, not 200 issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Coda API writes return 202, not 200.

## Variant phrasings

### check mutation status with the requestId

## Why it happens

Coda API docs gap: write endpoints (insert, update, upsert, delete rows) do not apply edits synchronously. They return HTTP 202, meaning the edit was accepted and queued, and it can take a few seconds to apply or may fail if invalid.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.