Hubspot Property with label Source App ID is blocking the entire eComm Sync

[Vamsivinay119]

@Sean_Duane @Llewellyn_Smith @Isaac_Takushi

Below are the error messages for different portals we are seeing in the ecomm/v1/sync-errors end point. And none of our client's Contacts or Deals are syncing into their portals.

This is a big issue. Please look into this soon

I DMed you guys the PortalIDs and AppID.

{
"portalId": XXXXXX,
"objectType": "CONTACT",
"integratorObjectId": "XXXXXX",
"changeOccurredTimestamp": 1540922787000,
"errorTimestamp": 1540922789607,
"type": "INVALID_ENUM_PROPERTY",
"details": "Invalid enum property [ip__ecomm_bridge__source_app_id] value [;XXXXX]. Valid options: [[0]]",
"status": "OPEN"
},
{
"portalId": XXXXXX,
"objectType": "LINE_ITEM",
"integratorObjectId": "ORDERLINEITEM:XXXXXX",
"changeOccurredTimestamp": 1540922774000,
"errorTimestamp": 1540922775295,
"type": "INVALID_ENUM_PROPERTY",
"details": "Invalid enum property [ip__ecomm_bridge__source_app_id] value [;XXXXX]. Valid options: [[0]]",
"status": "OPEN"
},
{
"portalId": XXXXXX,
"objectType": "DEAL",
"integratorObjectId": "CHECKOUT:XXXXXX",
"changeOccurredTimestamp": 1540922773000,
"errorTimestamp": 1540922774777,
"type": "INVALID_ENUM_PROPERTY",
"details": "Invalid enum property [ip__ecomm_bridge__source_app_id] value [;XXXXX]. Valid options: [[0]]",
"status": "OPEN"
},
{
"portalId": XXXXXX,
"objectType": "CONTACT",
"integratorObjectId": "XXXXXX",
"changeOccurredTimestamp": XXXXXX,
"errorTimestamp": 1540922774737,
"type": "INVALID_ENUM_PROPERTY",
"details": "Invalid enum property [ip__ecomm_bridge__source_app_id] value [;XXXXX]. Valid options: [[0]]",
"status": "OPEN"
},
{
"portalId": XXXXXX,
"objectType": "PRODUCT",
"integratorObjectId": "1805038911601",
"changeOccurredTimestamp": XXXXXX,
"errorTimestamp": 1540922773097,
"type": "INVALID_ENUM_PROPERTY",
"details": "Invalid enum property [ip__ecomm_bridge__source_app_id] value [;XXXXX]. Valid options: [[0]]",
"status": "OPEN"
}

[Vamsivinay119]

Hi @Llewellyn_Smith,

So I check with the Bearer token for each client to get their errors. I think there should be a restriction set per Bearer token per integration in the eComm sync-errors.

As of now every ecomm sync error is displayed even if the client is using any integration using ecomm bridge API.

So far I think Unific and HS-Shopify Native are the only one's using ecomm bridge hence the errors displayed are from both the integrations.

In future if the client is using another integration using ecomm bridge then they will also be in the list of errors creating more chaos.

P.S : The client was using both HS-Shopify Native and Unific. They turned off HS-Native now.

[lsmith]

You're right, that's a real security issue. The intended behavior was to restrict the errors based on the access token, I'll fix now.

[lsmith]

Hi @Vamsivinay119,
I fixed the error for the above customer yesterday, but that error is not for your application. I'm curious, how did you find that sync error?

[IsaacTakushi]

Hi @Vamsivinay119,

@Sean_Duane will be on leave for a while, so please refrain from messaging him. I'll send you a direct message so you can share the unmasked response.

@Llewellyn_Smith, are you familiar with the issue Sean cited last week? Could this be related? Happy to connect on our end to dig in further.

[Vamsivinay119]

Sure thing. Please send me a message. @Isaac_Takushi

[Vamsivinay119]

Hi @Sean_Duane Thanks for getting back and fixing the issue soon.

Is there a way to alert either of HS or the client in future if issues like this occur?

I did see this issue when checking for some other stuff. Else I doubt I could still not know that this is happening.

[sduane]

Our sync errors need more loving, but I am not sure when we are going to work more on them.

Of the work, we want to give Users an errors screen that they can use to see most sync errors.
We also have talked about ways to bake this information into the developer portal, like Webhook logging, but more aggregated.

[Vamsivinay119]

Hi @Sean_Duane, We are seeing the similar error messages again today.

  {
            "portalId": XXXX,
            "objectType": "DEAL",
            "integratorObjectId": "cartToken-969cf0d628f79c2b905a4a796e903a41",
            "changeOccurredTimestamp": 1541536956000,
            "errorTimestamp": 1541536968849,
            "type": "INVALID_ENUM_PROPERTY",
            "details": "Invalid enum property [ip__ecomm_bridge__source_app_id] value [;XXX]. Valid options: [[0, XXXX]]",
            "status": "OPEN"
        }, 

Also, the integratorObjectId isn't correct. That is not what we send. Can you please check the same? I DMed you the unmasked message

[sduane · Accepted solution]

Thanks for pinging us about this. This was our fault, and we apologize for causing problems.

We identified the problem, filled that property enums options with valid ones.
New fast sync should work fine now.
Our resync process will run in a day or two to pick all the rest up.

Here's what happened:

• We added a new ecommbridge supplied property ip__ecomm_bridge__source_app_id
• This enum property automatically adds options as apps sync into that portal
• We ran a job to update the name of this property across all portals
• That job ended up resetting all valid property options for ip__ecomm_bridge__source_app_id
• We ran the backfill job that defines options for the property on all portals

Let me know if I can help clear anything up. Thanks again for reaching out about this!