A run can represent either a trace (root run) or a child run (~span).
interface RunCreateError message, captured if the run faces any issues.
Attachments for the example
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.
Unique identifier (UUID). Remains constant even if name changes.
Inputs that were used to initiate the run.
Display name (can be updated).
Outputs produced by the run, if any.
ID of a parent run, if this run is part of a larger operation.
ID of an example that might be related to this 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.
Tags for further categorizing or annotating the run.
Unique ID assigned to every run within this nested trace. *