-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Labels
pythonv1.0Features being tracked for the version 1.0 GAFeatures being tracked for the version 1.0 GAworkflowsRelated to Workflows in agent-frameworkRelated to Workflows in agent-framework
Description
Currently, workflow can get ID from two places:
- Randomly generated at build time
- From a checkpoint
The Id is also managed by 3 entities during runtime:
- The workflow object itself
- The runner
- The runner context
We are currently doing nothing to make sure the ID in these 3 places stay in sync.
We should consider a way to have a non-random identifier for workflow. Currently, the traces from different workflow instances are separated because their IDs are different. This creates an issue when you have a persisted session, which creates different instances of workflows but following the same checkpoint state lineage. In this case, there isn't a way to "join" these separate traces from different instances.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
pythonv1.0Features being tracked for the version 1.0 GAFeatures being tracked for the version 1.0 GAworkflowsRelated to Workflows in agent-frameworkRelated to Workflows in agent-framework
Type
Projects
Status
Done