Hello - I’m using a reverse ETL (Census) to sync data from our postgres db to hubspot. The query has worked find for months but as of 9:30am PST yesterday started returning the below error on a growing number of records. Nothing was touched so I feel like it has to be on the Hubspot side. Pipeline as an example is a set number so no idea why this error would start? Any help? (ps: I’m not a dev, semi-dangerous in SQL).
TypeCastErrors: dealstage must be a valid enum. Available options: [] | hubspot_owner_id must be a valid enum. Available options: [] | pipeline must be a valid enum. Available options: []
I’ve hit similar 502 errors before when doing Reverse ETL syncs. Usually, it comes down to hitting HubSpot’s API rate limits or temporary server issues. I’d first try spacing out your API requests a bit more or adding retries with exponential backoff—often that clears things up. If those tweaks don’t fix it, another quick alternative is using a different integration tool like Skyvia, since it’s pretty solid at handling these syncs smoothly.
Hi @AKlobnock , that error usually means HubSpot no longer recognizes the values you’re sending for pipeline, dealstage, or owner.
First check natively if someone edited or deleted a deal pipeline/stage around the time things broke: Settings > Objects > Deals > Pipelines. If a stage was removed or a new pipeline became default, your sync will fail until you update mappings (Set up and manage object pipelines )
Then switch your Reverse ETL to send internal IDs, not labels. Pull the current deal pipeline and stage IDs from the Pipelines API and refresh your Census mapping accordingly; renames keep the same ID, deletes do not (Accounts Dashboard | HubSpot )
Do the same for hubspot_owner_id by confirming that each owner still exists and has an active seat; if an owner was deactivated, remap to a valid owner. One quick safeguard is to upsert on record ID and ignore rows whose target pipeline/stage/owner don’t resolve, then fix those source rows and replay.
When this hinges on reliable two-way sync, Stacksync keeps HubSpot and your source in two-way sync, which prevents these clean-up cycles.