The following situations can increase ABORTED errors:
A document receiving too many updates per second.
Contention from overlapping transactions.
Traffic increases that exceed the 500-50-5 rule or encounter hot-spots.
ABORTED
Too much contention on these datastore entities. Please try again.
Or
ABORTED
Aborted due to cross-transaction contention. This occurs when multiple
transactions attempt to access the same data, requiring Firestore to abort at
least one in order to enforce serializability.
To resolve this issue:
For rapid traffic increases, Firestore attempts to automatically
scale to meet the increased demand. When Firestore
scales, latency begins to decrease.
Hot-spots limit the ability of Firestore to scale up, review
designing for scale to identify hot-spots.
The following situations can cause INVALID_ARGUMENT errors:
Attempting to commit a document with an indexed field value greater than
1,500 bytes. This limits applies to the UTF-8 encoding of the field value.
Attempting to commit a document with un-indexed field values greater
than 1,048,487 bytes (1 MiB - 89 bytes). This limit applies to the sum
of the field values in a document. For example, four fields of 256 KiB each
exceed the limit.
1,500 bytes (indexed) and 1,048,487 bytes (un-indexed) are
limits for field values. You cannot
exceed these limits and they are not quotas that can be
adjusted.
INVALID_ARGUMENT: The value of property field-name is longer than 1500 bytes
or
INVALID_ARGUMENT: The value of property field_name is longer than 1048487 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.
For un-indexed field values, split the field into multiple fields
or implement compression for the field value.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Understand error codes\n======================\n\nThis page lists error codes that you might encounter and provides suggestions for\nhow to fix each of them.\n\n### DEADLINE_EXCEEDED\n\nThe following can increase `DEADLINE_EXCEEDED` errors:\n\n- An increase in latency caused an operation take longer than the deadline (60 seconds by default) to complete.\n\n```\nDEADLINE_EXCEEDED\n\nA deadline was exceeded on the server.\n```\n\nTo resolve this issue, see the [guide to troubleshooting latency](/firestore/docs/resolve-latency).\n\n### ABORTED\n\nThe following situations can increase `ABORTED` errors:\n\n- A document receiving too many updates per second.\n- Contention from overlapping transactions.\n- Traffic increases that exceed the 500-50-5 rule or encounter hot-spots.\n\n```\nABORTED\n\nToo much contention on these datastore entities. Please try again.\n```\n\nOr \n\n```\nABORTED\n\nAborted due to cross-transaction contention. This occurs when multiple\ntransactions attempt to access the same data, requiring Firestore to abort at\nleast one in order to enforce serializability.\n```\n\nTo resolve this issue:\n\n- For rapid traffic increases, Firestore attempts to automatically scale to meet the increased demand. When Firestore scales, latency begins to decrease.\n- Hot-spots limit the ability of Firestore to scale up, review [designing for scale](./best-practices#designing_for_scale) to identify hot-spots.\n- Review [data contention in transactions](./transaction-data-contention) and your usage of transactions.\n- Reduce the write rate to individual documents.\n\n### RESOURCE_EXHAUSTED\n\nThe following situations can lead to `RESOURCE_EXHAUSTED` errors:\n\n- You exceeded the [free tier quota](https://cloud.google.com/firestore/quotas#free-quota) and billing is not enabled for your project.\n\n```\nRESOURCE_EXHAUSTED\n\nSome resource has been exhausted, perhaps a per-user quota, or perhaps the entire file system is out of space.\n```\n\nTo resolve this issue:\n\n- Wait for the daily reset of your free tier quota or [enable billing for\n your project](/billing/docs/how-to/modify-project#enable_billing_for_a_project).\n\n### INVALID_ARGUMENT\n\nThe following situations can cause `INVALID_ARGUMENT` errors:\n\n- Attempting to commit a document with an **indexed** field value greater than 1,500 bytes. This limits applies to the UTF-8 encoding of the field value.\n- Attempting to commit a document with **un-indexed** field values greater than 1,048,487 bytes (1 MiB - 89 bytes). This limit applies to the sum of the field values in a document. For example, four fields of 256 KiB each exceed the limit.\n\n1,500 bytes (indexed) and 1,048,487 bytes (un-indexed) are\n[limits](/datastore/docs/concepts/limits) for field values. You cannot\nexceed these limits and they are not quotas that can be\nadjusted. \n\n```\nINVALID_ARGUMENT: The value of property field-name is longer than 1500 bytes\n```\n\nor \n\n```\nINVALID_ARGUMENT: The value of property field_name is longer than 1048487 bytes\n```\n\nTo resolve this issue:\n\n- 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.\n- For un-indexed field values, split the field into multiple fields or implement compression for the field value."]]
