A run can represent either a trace (root run) or a child run (~span).
class RunTree(beta) Set instead of project_name for an addressed run.
Attachments associated with the run. Each entry is a tuple of [mime_type, bytes]
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:
The epoch time at which the run ended, if applicable.
Error message, captured if the run faces any issues.
Events like 'start', 'end' linked to the run.
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.
Outputs produced by the run, if any.
ID of a parent run, if this run is part of a larger operation.
Unset for a run sent to an address.
ID of an example that might be related to this run.
Projects to replicate this run to with optional updates.
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.
Tags for further categorizing or annotating the run.
Unique ID assigned to every run within this nested trace. *
Add an event to the run tree.
Patch the run tree to the API.