Logs not opening due to checksum instability

Summary

Logs fail to open in the UI, showing infinite loading or "Failed to fetch" errors in browser console. This occurs when checksum validation failures during platform instability prevent spans from being properly written to or retrieved from brainstore. The issue typically affects logs created during the instability window, while newer logs load successfully once the underlying checksum issue is resolved.

Resolution Steps

If newer logs load successfully

Step 1: Check if logs are queryable via BTQL

Run a BTQL query to determine if the log data exists in the database.

SELECT * FROM project_logs('your-project-name') 
WHERE id IN ('your-log-id-here')

Step 2: Verify root span IDs in the database

The URL r= parameter maps to root_span_id, not id.

SELECT id, span_id, root_span_id, created, project_id, _object_delete
FROM logs2
WHERE root_span_id IN ('your-root-span-id')
   OR id IN ('your-log-id');

Step 3: Interpret results

If BTQL returns data but UI won't render, it's a data completeness issue. If no results, spans were likely lost during the checksum instability window and cannot be recovered.

If all logs fail to load

Step 1: Check for checksum errors in API logs

Look for checksum mismatch errors in your brainstore API and reader logs during the timeframe when logs were created.

Step 2: Verify BRAINSTORE_LOCKS_URI configuration

Ensure the BRAINSTORE_LOCKS_URI environment variable matches the value in your brainstore_env_checksum database table.

Step 3: Contact Braintrust support

If checksum configuration appears correct, provide specific log IDs, timestamps, and browser console errors for further investigation.