Skip to main content
Last updated on

Troubleshoot the Atlassian Audit Logs connector

Beta

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

Resolve common Atlassian Audit Logs connector errors, including authentication failures from invalid or expired API keys, Atlassian 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: Atlassian returned an HTTP 401 or 403 response. This usually means the API key isn't valid, someone revoked it, the key expired, or the key's organization doesn't have an active Atlassian Guard Standard, Atlassian Guard Premium, or Cloud Enterprise subscription.

Solution:

  1. Confirm that the API Key in the Unity Catalog connection matches an active API key in Atlassian.
  2. Confirm that the Organization ID in the connection matches the organization the API key belongs to.
  3. Confirm that the key's organization admin still has Organization admin permission, and that the organization has an active Atlassian Guard Standard, Atlassian Guard Premium, or Cloud Enterprise subscription.

For details, see Configure authentication to Atlassian.

Atlassian API rate limit exceeded​

Cause: Atlassian returned an HTTP 429 response. Atlassian limits the Query audit log events endpoint to 10 requests per minute per user and 10 requests per minute per API path. See the Atlassian Organizations REST API rate limits.

Solution:

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

Atlassian API temporarily unavailable​

Cause: Atlassian 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.

On this page