Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
Hubspot Extract to PubSub
Hubspot Extract to PubSub
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 1
    • Issues 1
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 0
    • Merge requests 0
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
  • Analytics
    • Analytics
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Cosmos
  • Modules
  • Hubspot Extract to PubSubHubspot Extract to PubSub
  • Issues
  • #9

Closed
Open
Created Nov 02, 2020 by external-000-gpide3-tbd@external-000-gpide3-tbdContributor

Retrigger publish_email_events when hasMore is true

Currently, for each time interval (start timestamp, end timestamp) the maximum number of fetched (and published) events is based on a predefined limit variable.

If the actual number of events within that time interval exceeds the limit variable, we would also like to fetch and publish these remaining events. The hasMore response field provides this information.

While hasMore returns true, consecutive requests should be made by defining the correct offset for each request (see code)

Edited Nov 02, 2020 by external-000-gpide3-tbd
Assignee
Assign to
- NOT IN USE - Hubspot Integration pilot
Milestone
- NOT IN USE - Hubspot Integration pilot (Past due)
Assign milestone
Time tracking