Why are my traces being automatically upgraded to extended retention?

Last updated: December 10, 2025

Overview

LangSmith automatically upgrades certain traces from base retention (14 days) to extended retention (400 days) when they meet specific conditions. This article explains what triggers these automatic upgrades and how to manage your extended retention usage.

What triggers automatic upgrades to extended retention?

By default, traces are automatically upgraded to extended retention (400 days) when any of the following occur:

  • Feedback is added (human or automated)

  • A Run Rule/Automation matches the trace

  • The trace is added to an Annotation Queue

This is mainly because traces that match these conditions are considered more valuable and worth keeping longer. If you've taken the time to add feedback, set up an automation to flag it, or queue it for review, LangSmith assumes you'll want to reference it beyond the 14-day base retention period.

Note: Adding a trace to a Dataset does NOT trigger an upgrade. Datasets store copies of inputs/outputs with indefinite retention, but the original trace follows its normal retention tier.

How to identify what's driving your extended retention usage

If you're seeing more extended retention traces than expected, check these areas:

  1. Settings > Automations - Look for active Run Rules, especially any with "extend only" enabled

  2. Project Settings - Check if any projects have their default trace tier set to "longlived"

  3. Annotation Queues - Any trace added to a queue is automatically upgraded

  4. Evaluators - Automated evaluators attached to projects add feedback, which triggers the upgrade

How to control automatic upgrades

There is no user-facing setting to disable automatic upgrades entirely. However, you can control this by:

  • Setting your workspace/project default trace tier to "shortlived" - New traces will default to base retention

  • Disabling Run Rules that you don't need - Reduces automation-triggered upgrades

  • Avoiding adding traces to Annotation Queues - Unless you need the extended retention

  • Setting usage limits - Cap extended retention traces per month in your workspace settings

Note: When your extended retention limit is reached, Run Rules, feedback, and annotation queues become inaccessible to prevent further auto-upgrades.

Related articles

Tags: retention, traces, extended retention, run rules, automations, annotation queues, feedback, usage limits