What happened
What this says
Current to 10 Oct 26HubSpot connector stopped syncing after token re-entry. Bethan traced the issue to query permission loss during customer's system migration. Three days of stale data eroded team confidence.
Problem: Three days without fresh client data; customer team lost confidence in data. Handling: Bethan analysed logs, identified successful authentication but timeout on data queries, and asked the customer's HubSpot admin to check query permissions. The issue was scoped-down permissions from a recent migration. Watch: Connector reliability is critical to retention. A stale brain erodes trust. Follow up to confirm the fix is stable and check whether future migrations need pre-planning.
Details
Updated 9 Oct 26Trail
- created · Jenna Price 6 Mar 2026 10:46Hi, the HubSpot connector is still not syncing. We re-entered the token yesterday but nothing came through. We're now three days without fresh client data. Is there a bigger issue here? What do we need to do? Thanks, Jenna
- public_reply · Bethan Lister 6 Mar 2026 11:55Thanks, Jenna. I can see you re-entered the token yesterday. Let me check the logs to see what happened after that.
- public_reply · Bethan Lister 9 Mar 2026 10:24I've looked at the logs. The connector made successful authentication calls after you re-entered the token, but the data queries are timing out. This points to a query permission issue in HubSpot – likely from your migration. Can you ask your HubSpot admin to check whether the API user still has permissions to run queries on the accounts and contacts objects?
- internal_note · Bethan Lister 9 Mar 2026 12:15HubSpot auth successful but queries timing out. Query permissions were scoped down during migration. Need customer's HubSpot admin to grant query access on core objects.
- public_reply · Jenna Price 9 Mar 2026 14:48Sorry for the slow reply – the team's stretched. We've asked our HubSpot admin to check the permissions. Should hear back soon. Thanks, Jenna
- status_change · 13 Mar 2026 23:59