Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Important
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Azure Databricks previews.
This page describes common errors you might encounter with the managed Aha! connector and how to resolve them.
Pipeline fails to authenticate
The Aha! API returns an HTTP 401 or 403 response, and the connector fails the pipeline.
Cause: The API key is not valid, the user has revoked it, or the connection has the wrong subdomain.
Solution:
Generate a new API key and confirm the subdomain. See Configure authentication to Aha!. Then update the credentials on the connection. See Create an Aha! connection.
Requests are rate-limited
The Aha! API returns an HTTP 429 response.
Cause: Aha! allows up to 300 requests per minute and up to 20 requests per second, and applies the limit per account. Other API users on the same account count toward the limit. See Aha! API rate limiting.
Solution:
The connector waits and retries automatically, so transient rate limiting resolves on its own. If pipelines fail repeatedly, reduce other API usage on the Aha! account or schedule the pipeline less frequently.
Pipeline fails with a transient error
The Aha! API returns an HTTP 500, 502, 503, or 504 response.
Cause: The Aha! API is temporarily unavailable.
Solution:
The connector retries these responses automatically with exponential backoff. If the pipeline keeps failing, rerun it after the Aha! service recovers.