Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR exposes the ability to emit per-clock flow run labels, in addition to exposing
labels
onClient.create_flow_run
. This will enable the ability for users to schedule Flows to run simultaneously in different places / through different agents, and moreover will allow users to create ad-hoc runs with unique label sets as needed.Importance
This is a new feature that enables a pattern that wasn't possible before; please note this will not be available in Cloud / Server until the scheduler logic has been updated and released! We will try to have this released prior to the next release of Core 👍
Checklist
This PR:
changes/
directory (if appropriate)docs/outline.toml
for API reference docs (if appropriate)