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

Workflow restart after it ran to completion - better UX #6273

Closed
MetRonnie opened this issue Jul 31, 2024 · 2 comments
Closed

Workflow restart after it ran to completion - better UX #6273

MetRonnie opened this issue Jul 31, 2024 · 2 comments
Labels
could be better Not exactly a bug, but not ideal.

Comments

@MetRonnie
Copy link
Member

MetRonnie commented Jul 31, 2024

Problem

Copied from Element

@MetRonnie:
I have seen several instances of users trying to restart workflows that have already ran to completion, and seemingly being confused by why nothing is happening.

Proposed Solution

@MetRonnie:
Perhaps we need to make it clearer in the UI what is going on? And perhaps extend the 2 minute restart timer to something like 10 mins to give them enough time to figure out what intervention they need to make?

@hjoliver:
Good idea. I think we planned to have some kind of scrolling list of scheduler warnings in the GUI. For the moment maybe the big warning banner at top would do for this, if we can get the right information across.

Two easy things we could do:

  • Increase PT2M restart timer to say PT10M
  • Add a new workflow status message for "run to completion"
@MetRonnie MetRonnie added the could be better Not exactly a bug, but not ideal. label Jul 31, 2024
@MetRonnie MetRonnie added this to the 8.x milestone Jul 31, 2024
@oliver-sanders
Copy link
Member

oliver-sanders commented Jul 31, 2024

Sounds good to me.

The most likely case for users to encounter this is when trying to extend/continue a completed workflow run. Point anyone with this use case at the "extending workflow" example (which avoids this issue) - https://cylc.github.io/cylc-doc/nightly_8.4/html/user-guide/examples/extending-workflow/index.html

Note, there is also an issue to introduce a workflow status (not just status message) for completed workflows which would be useful in a variety of applications (e.g. rose-stem, sub-workflows & housekeeping old runs).

#5701

@oliver-sanders
Copy link
Member

Some of these things have now been actioned, closing this issue as a duplicate of #5474

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
could be better Not exactly a bug, but not ideal.
Projects
None yet
Development

No branches or pull requests

2 participants