Hey @cclark2 , what you’re seeing is expected behavior with HubSpot’s native Data Sync integrations.
Under the hood, the Airtable sync runs on a polling model.
HubSpot periodically checks for changes rather than reacting instantly to them. In practice, that means updates are usually picked up every 5–10 minutes, but depending on timing, load, and object volume, it’s normal to occasionally see delays closer to 12–15 minutes. There isn’t a guaranteed SLA-style sync interval you can rely on, and there’s no setting to tighten it.
That polling cadence also explains why you can’t control sync order. With standard integrations, HubSpot doesn’t expose any way to prioritize Tickets over other objects. Everything is queued and processed based on internal scheduling. As Seala mentioned, HubSpot generally prefers core objects to sync first so associations resolve cleanly, but that’s not configurable.
As of how HubSpot works today, there’s also no way to switch a native Airtable sync to an event-driven or webhook-based model. If your workflow needs near-real-time behavior, predictable ordering, or “tickets must go first” guarantees, you’re outside what the built-in integration was designed for. At that point, the only real option is a custom integration that reacts to changes as they happen instead of waiting for the next poll (Accounts Dashboard | HubSpot )
Small disclaimer since I’m close to this space: I work at Stacksync. We see teams move away from native syncs when these timing gaps become operationally painful, because a real-time, bidirectional sync removes the polling delay and lets you control how objects flow between systems. Not a fit for every setup, but that’s usually the tradeoff point. Hope this gives you a clearer picture of what’s possible and what isn’t.