Add FAQ for Common Error in HubSpot Cloud Mode #6244
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Customers who use HubSpot Cloud Mode and have an “Upsert Contact” mapping and “CBE” mapping, receive a contact already exists error with two other responses, see below:
Response 1:
"category": "EXPIRED_AUTHENTICATION",
"message": "The OAuth token used to make this call expired 7 second(s) ago.",
"statusCode": 401,
"statusMessage": "Unauthorized"
Reason for Error: Because the token was expired on the first request, we refreshed the token and then made the request again, see below.
Response 2:
"message": "resource not found",
"statusCode": 404,
"statusMessage": "Not Found"
Reason for Error: On this request, the contact was not found, so we then proceeded with the second request to attempt to create the contact.
Response 3:
"category": "CONFLICT",
"message": "Contact already exists. Existing ID: 11430351",
"statusCode": 409,
"statusMessage": "Conflict"
Reason for Error: This final request failed because of a Conflict error stating that the contact already exists. This is somewhat counterintuitive, being that when we first tried to update an existing contact, the response indicated that the contact did not exist. Read more from HubSpot here.
Merge timing
Related issues (optional)