Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Edit Message of Restart Button for More Clarity #1247

Open
marvin-robot opened this issue Mar 4, 2022 · 0 comments
Open

Edit Message of Restart Button for More Clarity #1247

marvin-robot opened this issue Mar 4, 2022 · 0 comments

Comments

@marvin-robot
Copy link
Member

Opened from the Prefect Public Slack Community

thomasopsomer.enpc: Hello community 🙂
We experienced a strange behaviour of the "restart" button on prefect cloud:
When going to a task run and restarting the task, it correctly reschedules the task, but it doesn't reschedule the downstream tasks (in the UI they stay green instead of light blue)

kevin701: Only Failed tasks are re-scheduled with the restart button. We know there are cases where you want to re-run upstream/downstream so for Orion (Prefect 2.0) this will be supported first-class with subflows being logical units that you can restart together

thomasopsomer.enpc: Ah ok. So the fact that it used to work was just luck ? 🙂
Then maybe you should update the message in the UI when clicking the restart button to specify that only the failed/not_successful downstream dependents will be re-run

kevin701: Ah ok we can add a ticket in the UI repo for that

kevin701: Do you know what current one was?

thomasopsomer.enpc: yep:
> Click on confirm to restart the flow run flow_run_name from this task run. This will restart your flow run and re-run task task_name and its downstream dependents.

kevin701: Thank you!

kevin701: <@ULVA73B9P> open “Edit Message of Restart Button for More Clarity” in UI

Original thread can be found here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant