This page lists error codes that you might encounter and provides suggestionsfor how to fix each of them.

DeadlineExceeded (262)

The following can increaseDeadlineExceeded (262) errors:

• An increase in latency caused an operation to take longer than the deadline(60 seconds by default) to complete.

DeadlineExceeded (262): Deadline exceeded.

To resolve this issue, see theguide to troubleshooting latency.

Aborted (112)

The following situations can increaseAborted (112) errors:

• A document receiving too many updates per second.
• Contention from overlapping transactions.
• Traffic that increases rapidly or encounters hot-spots.

Aborted (112): Too much contention on these documents. Please try again

Or

Aborted (112): Aborted due to cross-transaction contention. This occurs whenmultiple transactions attempt to access the same data, requiring at least oneto be aborted in order to enforce serializability.

To resolve this issue:

• For rapid traffic increases,Cloud Firestore attempts to automaticallyscale to meet the increased demand. WhenCloud Firestorescales, latency begins to decrease.
• Hot-spots limit the ability ofCloud Firestore to scale up. Reviewdesigning for scale to identify hot-spots.
• Reviewdata contention in transactions and yourusage of transactions.
• Reduce the write rate to individual documents.

InvalidArgument (2)

The following situations can causeInvalidArgument (2) errors:

• Attempting to commit a document with that exceeds the 7.5 KiB limit for anindex entry.

7.5 KiB is alimit for index entries. You cannot exceed this limitand it's not a quota that can be adjusted.

InvalidArgument (2): Index entry onfield_name is larger than 7680 bytes.

To resolve this issue:

For indexed field values, split thefield into multiple fields. If possible, create an un-indexed fieldand move data that doesn't need to be indexed into the un-indexedfield.