Dokumen menerima terlalu banyak pembaruan per detik.
Pertentangan dari transaksi yang tumpang-tindih.
Peningkatan traffic yang melebihi aturan 500-50-5 atau mengalami hot spot.
ABORTED
Too much contention on these datastore entities. Please try again.
Atau
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.
Untuk menyelesaikan masalah ini:
Untuk peningkatan traffic yang cepat, Firestore akan mencoba melakukan penskalaan secara otomatis untuk memenuhi peningkatan permintaan. Saat Firestore diskalasikan, latensi mulai menurun.
Hotspot membatasi kemampuan Firestore untuk melakukan penskalaan, tinjau
mendesain untuk skala guna mengidentifikasi hotspot.
Situasi berikut dapat menyebabkan error INVALID_ARGUMENT:
Mencoba melakukan commit dokumen dengan nilai kolom diindeks yang lebih besar dari
1.500 byte. Batas ini berlaku untuk encoding UTF-8 nilai kolom.
Mencoba melakukan commit dokumen dengan nilai kolom yang tidak diindeks yang lebih besar dari 1.048.487 byte (1 MiB - 89 byte). Batas ini berlaku untuk jumlah
nilai kolom dalam dokumen. Misalnya, empat kolom dengan ukuran masing-masing 256 KiB melebihi batas.
1.500 byte (terindeks) dan 1.048.487 byte (tidak terindeks) adalah
batas untuk nilai kolom. Anda tidak dapat melebihi batas ini dan batas ini bukan kuota yang dapat disesuaikan.
INVALID_ARGUMENT: The value of property field-name is longer than 1500 bytes
atau
INVALID_ARGUMENT: The value of property field_name is longer than 1048487 bytes
Untuk menyelesaikan masalah ini:
Untuk nilai kolom yang diindeks, bagi kolom menjadi beberapa kolom. Jika memungkinkan, buat kolom yang tidak terindeks dan pindahkan data yang tidak perlu diindeks ke kolom yang tidak terindeks.
Untuk nilai kolom yang tidak diindeks, pisahkan kolom menjadi beberapa kolom atau terapkan kompresi untuk nilai kolom.
[[["Mudah dipahami","easyToUnderstand","thumb-up"],["Memecahkan masalah saya","solvedMyProblem","thumb-up"],["Lainnya","otherUp","thumb-up"]],[["Sulit dipahami","hardToUnderstand","thumb-down"],["Informasi atau kode contoh salah","incorrectInformationOrSampleCode","thumb-down"],["Informasi/contoh yang saya butuhkan tidak ada","missingTheInformationSamplesINeed","thumb-down"],["Masalah terjemahan","translationIssue","thumb-down"],["Lainnya","otherDown","thumb-down"]],["Terakhir diperbarui pada 2025-09-04 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."]]
