Our data team is receiving errors when batch uploading data via API.
They sent 312 batches of 100, and 45 batches failed due to errors, which totals 4,500 accounts for us. Some errors were due to invalid email address typos, but we cannot figure out the reason for the other rejections. See errors below. Could you please tell us what these mean and how to fix?
4 files = {“status”:“error”,“message”:“There was an error processing the request.”,“correlationId”:“89af5e10-a33b-41af-a348-477c8f781766”,“category”:“INTERNAL_ERROR”}
36 files = {“status”:“error”,“message”:“Cannot set PropertyValueCoordinates{portalId=45960257, objectTypeId=ObjectTypeId{legacyObjectType=CONTACT}, propertyName=acct_id, value=139953698} on 177524384095. 161659393086 already has that value.”,“correlationId”:“fa4f315f-d518-4f2d-aa6d-09dc0002cd99”,“category”:“VALIDATION_ERROR”}
For error #2, we assumed this meant that a duplicate record is already in HubSpot. We tested some of the account IDs in the error code (see below), and they are in HubSpot already, coming from our data team between Sept. and Oct. but we are not sure why it is not automatically updated/the entire batch is rejected. Please advise.
2025-11-21 12:33:55.947 -05:00 [Fatal ] {“status”:“error”,“message”:“Cannot set PropertyValueCoordinates{portalId=45960257, objectTypeId=ObjectTypeId{legacyObjectType=CONTACT}, propertyName=acct_id, value=139266828} on 177479435858. 154245081191 already has that value.”,“correlationId”:“9d67f874-48c9-41ba-ad07-0180a657f3af”,“category”:“VALIDATION_ERROR”}
2025-11-21 12:34:34.504 -05:00 [Fatal ] {“status”:“error”,“message”:“Cannot set PropertyValueCoordinates{portalId=45960257, objectTypeId=ObjectTypeId{legacyObjectType=CONTACT}, propertyName=acct_id, value=142644422} on 177478197851. 154246170237 already has that value.”,“correlationId”:“5935c8d5-2a86-45e4-8201-4d26e2cab6cb”,“category”:“VALIDATION_ERROR”}
2025-11-21 12:34:34.997 -05:00 [Fatal ] {“status”:“error”,“message”:“Cannot set PropertyValueCoordinates{portalId=45960257, objectTypeId=ObjectTypeId{legacyObjectType=CONTACT}, propertyName=acct_id, value=143368386} on 177481293222. 161669627735 already has that value.”,“correlationId”:“5cbd4101-fd33-4d66-8195-e6757fd3cf50”,“category”:“VALIDATION_ERROR”}
2025-11-21 12:36:44.840 -05:00 [Fatal ] {“status”:“error”,“message”:“Cannot set PropertyValueCoordinates{portalId=45960257, objectTypeId=ObjectTypeId{legacyObjectType=CONTACT}, propertyName=acct_id, value=140196630} on 177528727076. 153190986387 already has that value.”,“correlationId”:“4730e5a1-66fa-400b-bcc2-6d105b6ba1f8”,“category”:“VALIDATION_ERROR”}
2025-11-21 12:36:45.419 -05:00 [Fatal ] {“status”:“error”,“message”:“Cannot set PropertyValueCoordinates{portalId=45960257, objectTypeId=ObjectTypeId{legacyObjectType=CONTACT}, propertyName=acct_id, value=142630863} on 177523910187. 153152065832 already has that value.”,“correlationId”:“63548dff-db59-45af-adb7-6b5cb88e6006”,“category”:“VALIDATION_ERROR”}
Our data team is receiving errors when batch uploading data via API.
They sent 312 batches of 100, and 45 batches failed due to errors, which totals 4,500 accounts for us. Some errors were due to invalid email address typos, but we cannot figure out the reason for the other rejections. See errors below. Could you please tell us what these mean and how to fix?
4 files = {“status”:“error”,“message”:“There was an error processing the request.”,“correlationId”:“89af5e10-a33b-41af-a348-477c8f781766”,“category”:“INTERNAL_ERROR”}
36 files = {“status”:“error”,“message”:“Cannot set PropertyValueCoordinates{portalId=45960257, objectTypeId=ObjectTypeId{legacyObjectType=CONTACT}, propertyName=acct_id, value=139953698} on 177524384095. 161659393086 already has that value.”,“correlationId”:“fa4f315f-d518-4f2d-aa6d-09dc0002cd99”,“category”:“VALIDATION_ERROR”}
For error #2, we assumed this meant that a duplicate record is already in HubSpot. We tested some of the account IDs in the error code (see below), and they are in HubSpot already, coming from our data team between Sept. and Oct. but we are not sure why it is not automatically updated/the entire batch is rejected. Please advise.
2025-11-21 12:33:55.947 -05:00 [Fatal ] {“status”:“error”,“message”:“Cannot set PropertyValueCoordinates{portalId=45960257, objectTypeId=ObjectTypeId{legacyObjectType=CONTACT}, propertyName=acct_id, value=139266828} on 177479435858. 154245081191 already has that value.”,“correlationId”:“9d67f874-48c9-41ba-ad07-0180a657f3af”,“category”:“VALIDATION_ERROR”}
2025-11-21 12:34:34.504 -05:00 [Fatal ] {“status”:“error”,“message”:“Cannot set PropertyValueCoordinates{portalId=45960257, objectTypeId=ObjectTypeId{legacyObjectType=CONTACT}, propertyName=acct_id, value=142644422} on 177478197851. 154246170237 already has that value.”,“correlationId”:“5935c8d5-2a86-45e4-8201-4d26e2cab6cb”,“category”:“VALIDATION_ERROR”}
2025-11-21 12:34:34.997 -05:00 [Fatal ] {“status”:“error”,“message”:“Cannot set PropertyValueCoordinates{portalId=45960257, objectTypeId=ObjectTypeId{legacyObjectType=CONTACT}, propertyName=acct_id, value=143368386} on 177481293222. 161669627735 already has that value.”,“correlationId”:“5cbd4101-fd33-4d66-8195-e6757fd3cf50”,“category”:“VALIDATION_ERROR”}
2025-11-21 12:36:44.840 -05:00 [Fatal ] {“status”:“error”,“message”:“Cannot set PropertyValueCoordinates{portalId=45960257, objectTypeId=ObjectTypeId{legacyObjectType=CONTACT}, propertyName=acct_id, value=140196630} on 177528727076. 153190986387 already has that value.”,“correlationId”:“4730e5a1-66fa-400b-bcc2-6d105b6ba1f8”,“category”:“VALIDATION_ERROR”}
2025-11-21 12:36:45.419 -05:00 [Fatal ] {“status”:“error”,“message”:“Cannot set PropertyValueCoordinates{portalId=45960257, objectTypeId=ObjectTypeId{legacyObjectType=CONTACT}, propertyName=acct_id, value=142630863} on 177523910187. 153152065832 already has that value.”,“correlationId”:“63548dff-db59-45af-adb7-6b5cb88e6006”,“category”:“VALIDATION_ERROR”}
Out of the 312 batch uploads (100 records per batch), 45 batches failed due to two distinct error types. The first error category, labeled as INTERNAL_ERROR, occurred in four files and indicates a temporary server-side issue on HubSpot’s end rather than a problem with the data itself. These errors typically happen due to transient processing failures, high API load, or timeouts. The recommended resolution for these cases is to retry the affected batches after a short delay or reprocess them in smaller batch sizes.
he second and more frequent error category, VALIDATION_ERROR, affected 36 files and is related to a unique property conflict involving the acct_id field on contact records. These errors occur when the API attempts to assign an acct_id value to a contact, but that same value already exists on another contact in HubSpot. Because acct_id is configured as a unique property,
To prevent these validation errors going forward, the integration must ensure that upserts are performed using a reliable unique identifier, such as email or a property explicitly configured as unique and intended for record matching. Incoming data should be checked against existing HubSpot records before assignment of unique values, ensuring that updates are applied to the correct contact rather than attempting to overwrite a unique field on a different record.
Hope it Helps!
Thanks for posting in the Community! Also, thank your @TG6 for your additional insight there!
Please feel free to let us know if your issue is still persisting here? If it is, and you find that you require further troubleshooting would you mind providing additional details about the endpoint you’re using, and an example request that failed?