Skip to main content
Last updated on

Troubleshoot the Strac connector

Beta

This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.

This page describes common errors you might encounter with the managed Strac connector and how to resolve them.

Strac API key not valid or unauthorized​

Cause: Strac returned an HTTP 401 or 403 response. The API key is missing, incorrect, or not authorized for the audit events endpoint. The connector treats this as a configuration error and fails the pipeline.

Solution:

  1. Confirm that the API Key in the Unity Catalog connection matches a current Strac API key and that it uses the correct sk_ prefix for your environment (sk_test_ or sk_live_).
  2. Confirm that the API Endpoint in the Unity Catalog connection matches the host and stage for the same environment.
  3. If the key is not valid or unauthorized, request a new key from Strac, update the connection with the new value, and run the pipeline again.

For details, see Configure authentication to Strac.

Strac API rate limit exceeded​

Cause: Strac returned an HTTP 429 response because the request rate exceeded the API's limit.

Solution:

The connector honors the Retry-After response header, then falls back to exponential backoff and retries automatically. If this happens repeatedly, reduce the pipeline's schedule frequency or the number of concurrent pipelines that share the same Strac API key.

Strac API temporarily unavailable​

Cause: Strac returned a transient server error (HTTP 500, 502, 503, or 504).

Solution:

The connector automatically retries with exponential backoff. If the issue persists, wait, then run the pipeline again.

On this page