Hex Ingestion Causing "Too Many Calls" API Error

Ingestion from Hex notebooks triggered API rate limiting errors, with messages indicating "Too many calls" to the Hex API. This prevented users from successfully ingesting Hex workspace metadata and resulted in incomplete or failed ingestion runs.

Common Error Messages:

• "Too many calls" API error
• Hex API rate limit exceeded
• 429 Too Many Requests

The Hex connector has been updated with proper rate limiting and request throttling to respect Hex API limits. The connector now: - Implements exponential backoff for retries - Spreads requests over time to avoid hitting rate limits - Batches API calls more efficiently

Configure Hex ingestion with rate limit awareness:

Example for Hex. This can be adapted for other notebook/BI platforms.

source:
  type: hex
  config:
    token: "${HEX_API_TOKEN}"

    # The connector now handles rate limiting automatically
    # No additional configuration required

    # Optional: Adjust if you have custom rate limits
    # requests_per_minute: 60

Fixed in version v0.3.11. If you continue to experience rate limiting issues, check your Hex API token permissions and your organization's Hex API limits. Consider scheduling ingestion during off-peak hours for large Hex workspaces.

• Hex Ingestion Source
• Rate Limiting Best Practices