[FIXED] Hubspot Integration Keeps Resetting Field Sync Settings

Occasionally, the Hubspot integration will fail for no apparent reason. When we try to enable it again by clicking the “Sync Now” button, it completely resets all the settings in the “Edit Fields to Sync” area and defaults back to syncing everything, even though we had previously set many, many fields to not sync.

We have 300+ fields in Hubspot, (even though Fibery only allows a max of 210) so every time this happens, we need to spend a good half-hour unsyncing all the fields again, which is very frustrating.

Hopefully there’s a log that could be looked at on our workspace to help figure out why this keeps happening and have a fix implemented!

Thank for reporting.
We are aware of this issue and I’m on it. I will let you know when it’s fixed

1 Like

@interr0bangr how do you think, this happens randomly or after some change in Hubspot? Does anything come to your mind?

I just did a bunch of tests to try and force the issue to happen but couldn’t replicate though basic usage.

My guess is that is that behind the scenes (whether it’s on Fibery’s side, like yesterday, or on Hubspot’s side in other cases) the integration gets disconnected and then when it reconnects it just completely ignores any existing settings and starts from scratch.

I would understand why this would happen if the user triggered this, since you warn them this will happen with a big popup if they click “Disconnect and Migrate” or “Remove and Delete”

But if the disconnection and reconnection is NOT triggered by the user themselves and is caused by either the Fibery or Hubspot systems, I would hope the existing settings from the last successful sync would be retained and it would not be treated like a completely new integration.

Happy to work with whoever needed to test and fix this! In addition to the time required to update all the settings again, it completely breaks many rules and formulas we’ve created across other databases in Fibery that are fed by the Hubspot databases.

@interr0bangr that should be fixed now. Please let us know in case your config gets reset again