The dotted order for the run.
This is a string composed of {time}{run-uuid}.* so that a trace can be sorted in the order it was executed.
Example:
Any additional metadata or settings for the run.
Optionally, a unique identifier for the run.
Inputs that were used to initiate the run.
A human-readable name for the run.
Specifies the type of run (tool, chain, llm, etc.).
Serialized state of the run for potential future use.
The epoch time at which the run started, if available.
Unique ID assigned to every run within this nested trace. *
OptionalattachmentsAttachments associated with the run. Each entry is a tuple of [mime_type, bytes]
Optionalend_The epoch time at which the run ended, if applicable.
OptionalerrorError message, captured if the run faces any issues.
OptionaleventsEvents like 'start', 'end' linked to the run.
OptionaloutputsOutputs produced by the run, if any.
Optionalparent_Optionalparent_ID of a parent run, if this run is part of a larger operation.
Optionalreference_ID of an example that might be related to this run.
OptionalreplicasProjects to replicate this run to with optional updates.
OptionaltagsTags for further categorizing or annotating the run.
OptionaltracingAdd an event to the run tree.
A single event or string to add
Optionaloptions: { excludeInputs?: boolean }Optionalheaders: HeadersLikeStaticfromStaticfromOptionalinheritArgs: Partial<RunTreeConfig>StaticfromStaticget
A run can represent either a trace (root run) or a child run (~span).