HubSpot - INVALID_OPTION Error

This error will either appear in your Dashboard's activity feed or in your Transaction Report.

Error Message Example

422 Unprocessable Entity / upstream error / {'upstreamCode': 400, 'upstreamError': 'Bad Request', 'upstreamDetail': {'errorData': [{'validationResults': [{'isValid': False, 'error': 'INVALID_OPTION', 'name': 'account_status', 'message': 'Tech Issue - Performance was not one of the allowed options:

This is an error sent back by HubSpot. It means that during an attempt to write a record, a value from the other system that was trying to write into a Drop Down Select field was INVALID. In other words, this value does not exist as one of the drop down options in the given field, in this case of this particular error, the account_status field.

This error can often be quite long as it will also include a list of all the available field values that exist within the HubSpot field that is throwing this error.

How to Resolve

Follow these steps to resolve this issue and re-sync records that may have failed to write due to this conflict.

Step 1: Edit field properties in your HubSpot portal

Login to your HubSpot portal and go to the Property settings section to find the field in question. Edit this drop down field and add in the value(s) that caused the conflict to occur. Make sure to match capitalization and punctuation exactly.

Step 2: Refresh Field Info in Bedrock

This is a simple step but critical to ensure that these updated values in HubSpot are recognized by your Bedrock integration.

Step 3: Re-Sync Record(s)

Whether you want to sync just one record that failed to write because of this conflict or many, you can use an On-Demand Trigger field to force records to go back through your integration. Don't have an On-Demand Trigger Sync field setup or not sure how these work? Check out this help article to set one up.

If enough records were impacted and you simply just want to perform a Full Sync, you can do so by  following the steps in this help article. A Full Sync is often the last resort since these can take some time to complete and you often want to run them over the weekend to avoid any conflicts with your teams day to day activities within your systems.