Hubspot engagements stream -- /recent vs /paged endpoint

Hey there, I’ve been trying to sync the engagements stream from Hubspot (v.0.3.0) but noticed I was only getting 10K records. Digging in a bit, it looks like it’s pulling data from the /recent endpoint which is limited to 10K records rather than the /paged endpoint which has everything (see here and here).

When I dug into the connector code, I saw this in

    def url(self):
        if self.state:
            return "/engagements/v1/engagements/recent/modified"
        return "/engagements/v1/engagements/paged"

So, it looks like if there is a state present, the connector will use the recent endpoint and if there isn’t a state present it will use the paged endpoint. The weird thing is, I’ve reset my data which should clear the state and it’s still using the recent endpoint for this stream.

Anyone else encounter this issue?

One other observation … the if-then logic is faulty as the connector requires a start date timestamp when setup. So the connector will always have a self.state set. Basically, as designed it can never use the /paged endpoint.

I’m not even sure why it’s necessary to make the distinction between the two endpoints. Shouldn’t the connector only use the /paged endpoint? There is no benefit (that I’m aware of) to using /recent.

I’ve built a custom version of the connector on my own that resolves this issue, and things seem to be working as expected now.

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

Good catch! Looks the endpoint paged won’t be used in the connector. I’m not sure if this is historical or some mistaken in implementation. Can you open a Github issue?