Troubleshoot the Box Audit Logs connector

Important

This feature is in Beta. To use it, a workspace admin must turn on Lakeflow Connect for Box Audit Logs from the Previews page. See Manage Azure Databricks previews.

Resolve common Box Audit Logs connector errors, including authentication failures from unauthorized apps or credentials that aren't valid, Box API rate limits, and transient service errors.

For general troubleshooting guidance that applies to all managed ingestion pipelines, see Troubleshoot managed ingestion pipelines.

Pipeline fails to authenticate

Cause: Box returned an HTTP 403 or 401 response. HTTP 403 is a configuration error and fails the pipeline. HTTP 401 triggers a token refresh and retry. If the retry still fails, treat it as invalid credentials.

This usually means the client ID or client secret isn't valid, the app isn't authorized in the Admin Console, the app is missing Manage enterprise properties, or the identity doesn't have report permission.

Solution:

1. Confirm that the Client ID, Client Secret, and Enterprise ID in the Unity Catalog connection match the Server Authentication app.
2. Confirm that an admin authorized the app. If you changed scopes or access level and Authorization is no longer Authorized, authorize the app again.
3. Confirm that Manage enterprise properties is selected on the Configuration tab.
4. Confirm that the identity is an enterprise admin, or a co-admin with Run new reports and access existing reports.

For details, see Configure authentication to Box.

Box API rate limit exceeded

Cause: Box returned an HTTP 429 response. Box generally limits API traffic to about 1,000 requests per minute per user. See Rate limits.

Solution:

The connector waits and retries automatically, honoring the Retry-After header when Box returns one. If this happens repeatedly, reduce the pipeline's schedule frequency or the number of concurrent pipelines that share the same Box app.

Box API temporarily unavailable

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

Solution:

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