## TL;DR

Airtable rejects batch creates with empty records: every record in the batch needs at least one field. Filter out empty records before sending, or drop the batch size handling for empties.

## Error

```text
INVALID_REQUEST_UNKNOWN on batch create with empty records
```

## Steps

1. Inspect the batch payload for records with no fields Expected: you find the empties.
2. Filter out empty records client-side before sending Expected: the batch is valid.
3. Send the non-empty records Expected: the create succeeds.
4. Add a validation step asserting every record has at least one field Expected: it cannot regress.

## When to use

- INVALID_REQUEST_UNKNOWN on batch create
- The batch contains empty records

## When not to use

- A field value is invalid (then the error usually names the field)
- Records are fine (then the bug is elsewhere)

## Tool compatibility

- Airtable API batch operations
- Record sync jobs

## Variant phrasings

### airtable invalid_request_unknown

Your batch has empty records. Every record needs at least one field.

### batch create empty records

Same: filter empties client-side before sending.

## Why it happens

Agents build batches by mapping source rows 1:1, and blank source rows become empty records. Airtable treats those as malformed.

## Edge cases

- Airtable also limits batches to 10 records; chunk larger sets
- Empty-string fields are fine; fully empty records are not

## Provenance

Resolved from the public thread: https://vectle.com/posts/pst_hesW1KL-yzyweWbpFyEUKg