-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Add hover-over text for ambiguous buttons #9541
Comments
Retry will run the existing failed workflow whereas resubmit will submit a new workflow with the same spec. |
Just to a little bit of clarity. |
It sounds like retry will only rerun the failed bits (and cascading following bits) whereas resubmit will start from scratch. A user shouldn't have to file a bug to find out that distinction, it should be clear from the documentation and it should be clear from the UI. The docs for each item should clearly indicate what the specific thing does and mention the other one and hint at when one would want to use the other instead, |
retry
and resubmit
Was looking to add this myself and then found this issue again. Gonna work on this in tandem with docs and help text changes for #11511 Would also like to add tooltips for Terminate vs. Stop as well. Terminate vs. Stop and Retry vs. Resubmit are perhaps the most frequently asked questions I've seen (and personally asked/searched for too). For anyone finding themselves here: |
One small complication here, these buttons are rendered via the |
Also for the CLI and its docs, I wrote up #11625 to describe |
Summary
Documentation and UX need to make it clear how
retry
andresubmit
differ.https://argoproj.github.io/argo-workflows/cli/argo_retry/
https://argoproj.github.io/argo-workflows/cli/argo_resubmit/
Use Cases
Someone trying to understand when to use
retry
and when to useresubmit
Message from the maintainers:
Love this enhancement proposal? Give it a 👍. We prioritise the proposals with the most 👍.
The text was updated successfully, but these errors were encountered: