The following situations can increase Aborted (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 when
multiple transactions attempt to access the same data, requiring at least one
to be aborted in order to enforce serializability.
To resolve this issue:
For rapid traffic increases, Cloud Firestore with MongoDB compatibility attempts to automatically
scale to meet the increased demand. When Cloud Firestore with MongoDB compatibility
scales, latency begins to decrease.
Hot-spots limit the ability of Cloud Firestore with MongoDB compatibility to scale up. Review
designing for scale to identify hot-spots.
The following situations can cause InvalidArgument (2) errors:
Attempting to commit a document with that exceeds the 7.5 KiB limit for an
index entry.
7.5 KiB is a limit for index entries. You cannot exceed this limit
and it's not a quota that can be adjusted.
InvalidArgument (2): Index entry on field_name is larger than 7680 bytes.
To resolve this issue:
For indexed field values, split the
field into multiple fields. If possible, create an un-indexed field
and move data that doesn't need to be indexed into the un-indexed
field.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-25 UTC."],[],[],null,["\u003cbr /\u003e\n\n\n|--------------------------------------------------------|\n| *Relevant to Cloud Firestore Enterprise edition only.* |\n\n\u003cbr /\u003e\n\nThis page lists error codes that you might encounter and provides suggestions\nfor how to fix each of them.\n\nDeadlineExceeded (262)\n\nThe following can increase `DeadlineExceeded (262)` errors:\n\n- An increase in latency caused an operation to take longer than the deadline (60 seconds by default) to complete.\n\n DeadlineExceeded (262): Deadline exceeded.\n\nTo resolve this issue, see the [guide to troubleshooting latency](/docs/firestore/enterprise/resolve-latency).\n\nAborted (112)\n\nThe following situations can increase `Aborted (112)` errors:\n\n- A document receiving too many updates per second.\n- Contention from overlapping transactions.\n- Traffic that increases rapidly or encounters hot-spots.\n\n Aborted (112): Too much contention on these documents. Please try again\n\nOr \n\n Aborted (112): Aborted due to cross-transaction contention. This occurs when\n multiple transactions attempt to access the same data, requiring at least one\n to be aborted in order to enforce serializability.\n\nTo resolve this issue:\n\n- For rapid traffic increases, Cloud Firestore with MongoDB compatibility attempts to automatically scale to meet the increased demand. When Cloud Firestore with MongoDB compatibility scales, latency begins to decrease.\n- Hot-spots limit the ability of Cloud Firestore with MongoDB compatibility to scale up. Review [designing for scale](/docs/firestore/enterprise/understand-reads-writes-scale#avoid_hotspots) to identify hot-spots.\n- Review [data contention in transactions](/docs/firestore/enterprise/understand-reads-writes-scale#high-level_steps_in_a_write_transaction) and your usage of transactions.\n- Reduce the write rate to individual documents.\n\nInvalidArgument (2)\n\nThe following situations can cause `InvalidArgument (2)` errors:\n\n- Attempting to commit a document with that exceeds the 7.5 KiB limit for an index entry.\n\n7.5 KiB is a [limit](/docs/firestore/enterprise/quotas) for index entries. You cannot exceed this limit\nand it's not a quota that can be adjusted. \n\n InvalidArgument (2): Index entry on \u003cvar class=\"readonly\" translate=\"no\"\u003efield_name\u003c/var\u003e is larger than 7680 bytes.\n\nTo resolve this issue:\n\nFor indexed field values, split the\nfield into multiple fields. If possible, create an un-indexed field\nand move data that doesn't need to be indexed into the un-indexed\nfield."]]
