Skip to main content
Applies to:
  • Plan -
  • Deployment -

​
Summary

Symptom: a trace shows a page-deletion-like event. Likely cause: an initial patch wrote escaped <page> markup that the detector flagged, then a later updatePage call removed that write. Recommended fix: inspect both the initial patch span and the later updatePage span; share the full trace context with support, or provide trace bytes via the CLI.

​
What is happening

An automated detector can flag a patch that contains escaped page markup as a deletion-like event. If a later updatePage call removes that bad write, the overall sequence can look like a transient deletion. The detector may report a false positive if it analyses only the first span instead of the full trace sequence. Trigger conditions:
  • A patch span includes escaped page markup, for example <page>.
  • A subsequent updatePage span undoes or removes that patch.
  • Analysis focuses on a single span or runs after the state has already been corrected.
Why you see it:
  • The initial patch contains the visible symptom: the escaped tag.
  • The corrective updatePage happens later and can be missed by fast or partial analysis.

​
Fix or suggestion

​
Option 1: Inspect the trace spans (most common fix)

  1. Open the full trace for the incident.
  2. Search spans for patch and updatePage calls in the same trace.
  3. Inspect the request body and timestamp for the first patch span. Look for escaped page markup, for example: 
    "<content>...<page>...</page>...</content>"
  4. Inspect the later updatePage span to confirm it removed or replaced the bad write.
  5. Share the trace ID, the relevant span IDs, and the short timestamp window with support. If support needs to inspect the trace directly, grant temporary workspace access before handoff.

​
Option 2: Provide trace bytes or use the CLI (alternative)

  1. Download the full trace bytes using your preferred tool or the Braintrust CLI.
  2. Use the correct Braintrust API base URL for your deployment:
    • US: https://api.braintrust.dev
    • EU: https://api-eu.braintrust.dev
    • Self-hosted: your configured Braintrust API base URL
  3. Attach the full trace file when requesting support, including the trace ID and timestamp window.
  4. If helpful, also include the matching patch and updatePage span payloads.
  5. Note time sensitivity: automated analysis is most useful when it can run within about 1 minute of receiving the trace.

​
How to confirm it worked

  • The initial patch span no longer contains escaped <page> markup, or a later updatePage span clearly shows the correction.
  • The detector no longer reports a deletion when analysis includes both spans.

​
Notes

A mitigation to reduce this false-positive detection is planned. When engaging support, include the full trace context and grant temporary workspace access only if direct inspection is needed.