You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: clarify that experiment run_name must be unique
When using the low-level SDK methods, the run_name must be unique per
dataset run. Reusing the same run_name silently prevents the new run
from appearing in the UI. Updated docs and code examples to explain
this and show timestamp-based run names as a good practice.
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: pages/docs/evaluation/experiments/experiments-via-sdk.mdx
+23-6Lines changed: 23 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1062,25 +1062,31 @@ Please refer to the [integrations](/docs/integrations/overview) page for details
1062
1062
1063
1063
### Run experiment on dataset
1064
1064
1065
-
When running an experiment on a dataset, the application that shall be tested is executed for each item in the dataset. The execution trace is then linked to the dataset item. This allows you to compare different runs of the same application on the same dataset. Each experiment is identified by a `run_name`.
1065
+
When running an experiment on a dataset, the application that shall be tested is executed for each item in the dataset. The execution trace is then linked to the dataset item. This allows you to compare different runs of the same application on the same dataset.
1066
+
1067
+
Each experiment is identified by a unique `run_name`. If you reuse the same `run_name`, the new run will not appear separately in the Langfuse dataset run UI. As a good practice, include a timestamp in your `run_name` to ensure uniqueness (the [Experiment Runner SDK](#experiment-runner-sdk) does this automatically).
// execute application function and get langfuseObject (trace/span/generation/event, and other observation types: see /docs/observability/features/observation-types)
1114
1123
// output also returned as it is used to evaluate the run
1115
1124
// you can also link using ids, see sdk reference for details
0 commit comments