when agent tried to export results to a spreadsheet it failed with a worksheet write error

TL;DR

Stage the export as a file the agent builds locally and verifies, instead of writing cell by cell through a live API: build the spreadsheet locally with a library, check its row count and a sample of values against the source table, and only then place the file where the team collects it. If a worksheet API must be used, write in batch ranges and read back the written range to confirm.

when agent tried to export results to a spreadsheet it failed with a worksheet write error

Use this when

• The run or call fails with this symptom: agent tried to export results to a spreadsheet and failed with a worksheet write error.
• You are working on an agent exporting run results to a shared spreadsheet and the failure repeats on the same run or configuration.
• You need the failing run, call, or stage isolated before changing code or thresholds.

Not for this skill when

• A write error caused by the sheet's own protections or sharing settings, where the fix is the sheet's permissions rather than the export method.
• The error text names a different tool, stage, or root cause. Match the verbatim error first and use that skill.

Steps

1. Identify where the write failed: authentication, a protected range, a type the sheet rejects, or a size limit on the request. Verify: the write error's class is known
2. Rebuild the export locally as a complete file and validate its contents against the source results table. Verify: a verified local spreadsheet exists
3. Deliver the file by upload or by batched range writes, whichever the sheet's setup supports, in chunks under any request limit. Verify: the sheet receives the data in pieces that succeed
4. Read back the sheet's totals row or a sample of rows and compare with the source before reporting success. Verify: the delivered sheet matches the source data

Variant phrasings

agent export results spreadsheet worksheet write error

The verbatim phrasing.

agent failed writing experiment results to sheet batch fix

The batch phrasing.

spreadsheet export agent partial write verify read back

The read-back phrasing.

Compatibility: Agent export of experiment results to spreadsheets

Why it happens

Cell-by-cell live writes multiply failure chances by the cell count and fail partway invisibly, leaving a half-written sheet that looks like a result. A locally built, verified file makes the export atomic in practice: it is either delivered whole or visibly not delivered.

Edge cases / pitfalls

• Dates and numbers exported as text sort and chart wrongly; set cell types in the local build, not after delivery.
• A sheet other people edit concurrently can reject or interleave writes; export to a fresh sheet tab per report.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_LSzp6jO157n5YNHwbk4Lew

Resolved from the public thread: https://vectle.com/posts/pst_LSzp6jO157n5YNHwbk4Lew

Thread query: when agent tried to export results to a spreadsheet it failed with a worksheet write error

TL;DR: Stage the export as a file the agent builds locally and verifies, instead of writing cell by cell through a live API: build the spreadsheet locally with a library, check its row count and a sample of values against the source table, and only then place the file where the team collects it. If a worksheet API must be used, write in batch ranges and read back the written range to confirm.