> ## Documentation Index
> Fetch the complete documentation index at: https://braintrust.dev/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Dashboard logs missing due to span name schema error

export const plans_0 = "Any"

export const deployments_0 = "Braintrust-hosted, Self-hosted"

export const data_plane_version_0 = undefined

export const use_case_0 = "Use case - Logging spans with invalid data types in the `name` field"

<Note>
  **Applies to:**

  * Plan - {plans_0}
  * Deployment - {deployments_0}
  * {data_plane_version_0}
  * {use_case_0}
</Note>

## Summary

**Issue:** Dashboard logs appear missing or incomplete when viewing spans in the Braintrust UI accompanied by the following error:

`Internal error: 'Schema error: 'Expected 1 column for path span_attributes_jsononame, but received more.'`

**Cause:** Invalid data types (such as JSON objects) are being passed to the `name` field of spans, which causes schema validation failures that silently hide affected logs from the dashboard view.

**Resolution:** Append additional valid logs to trigger a view refresh, and ensure span names are always strings.

## Resolution Steps

### Immediate Workaround

#### Step 1: Append new valid logs

Log additional spans to the same project to trigger a dashboard view refresh and display previously hidden logs.

### Permanent Fix

#### Step 1: Validate span name data types

Ensure all span `name` fields are strings, not objects or other data types.

```text theme={"theme":{"light":"github-light","dark":"github-dark-dimmed"}}
# Correct
braintrust.log(name="my-span-name", ...)

# Incorrect - will cause logs to be hidden
braintrust.log(name={"key": "value"}, ...)

```

#### Step 2: Check existing logging code

Review your codebase for any instances where non-string values are passed to the `name` parameter.