You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #11560, the backend made the pipeline version ID optional when creating a recurring run. When the pipeline version ID is not set, the latest pipeline version is always selected for each run.
What is the use case or pain point?
The user must use the API to create such recurring runs.
Is there a workaround currently?
You must use the API as a workaround.
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered:
Thanks for assigning yourself @akagami-harsh! One thought is that even though the user isn't selecting the pipeline version in this case, the UI can show the pipeline input parameters based on the latest pipeline version at that time.
Feature Area
/area frontend
What feature would you like to see?
In #11560, the backend made the pipeline version ID optional when creating a recurring run. When the pipeline version ID is not set, the latest pipeline version is always selected for each run.
What is the use case or pain point?
The user must use the API to create such recurring runs.
Is there a workaround currently?
You must use the API as a workaround.
Love this idea? Give it a 👍.
The text was updated successfully, but these errors were encountered: