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 SendGrid connector and how to resolve them.
Pipeline fails to authenticate
Cause: The pipeline stops with an authorization error when one of the following is true: the API key is not valid or has been rotated, the key is missing read access to the Subusers or IP Access Management data, or the account has IP Access Management enabled and the Databricks egress IP addresses are not on the allowlist.
Solution:
Confirm that the API key has read access to both the Subusers and IP Access Management APIs, following Configure authentication to SendGrid. If the key has been rotated, update the connection with the new key. See Create a SendGrid connection.
If your account has IP Access Management enabled, add the Azure Databricks serverless egress IP addresses to your SendGrid allowlist. SendGrid blocks API access from IP addresses that are not on the list. For more information, see IP Access Management in the SendGrid documentation.
Pipeline is rate limited
Cause: SendGrid throttles API requests when the connector exceeds the account's rate limit. The connector retries after the interval that SendGrid returns in the Retry-After response header.
Solution:
Reduce how frequently the pipeline runs so that each sync stays within the SendGrid rate limit. For more information on SendGrid rate limits, see Rate limits in the SendGrid documentation.