Troubleshoot the Anysphere Audit Logs connector
This feature is in Beta. Workspace admins can control access to this feature from the Previews page. See Manage Databricks previews.
Learn how to troubleshoot common issues with the Anysphere Audit Logs connector.
Pipeline fails to authenticate
If your pipeline fails to read from Anysphere (Cursor), verify the Admin API Key stored in your Unity Catalog connection matches the value in Anysphere (Cursor). Also verify that the key is a valid Admin API Key (crsr_...) created by a team admin in the Cursor dashboard — invalid or expired keys return a 403 Forbidden response. For the prerequisites and key creation steps, see Configure authentication to Anysphere (Cursor).
If the key is incorrect or has been rotated, create a new key in the Cursor dashboard and update the Unity Catalog connection. See Create an Anysphere Audit Logs connection.
Pipeline returns no data or empty table on first run
The audit_logs table contains only audit events from the last 30 days because Anysphere (Cursor) retains audit logs for approximately 30 days and caps the query window at 30 days. On the first pipeline run, expect the table to contain only recent events (typically from the last 30 days), not a full historical archive. This is expected behavior and not an error. Subsequent incremental runs will capture new audit events as they occur.