set status and/or message for failed workflows #13084
Replies: 4 comments 10 replies
-
|
Beta Was this translation helpful? Give feedback.
-
Let me try again ... Normally, I keep failed workflows for 1 week, so that somebody can take a look at them. That means, I already know about the ttl strategy because I'm using it to set I don't see how using
I don't understand that answer. I could identify the state "missing data" by checking the exit code of one particular step. So, in case I can't get rid of the workflow right away, alternatively I'd like to show a custom message right here: Is that possible? If yes, how? Simply put, I need one of those:
I am also open for alternative suggestions how to deal with such a scenario. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the explanation. It's still a little disappointing. I can't possibly be the only person, who thinks it might be a good idea to use the workflow message field to visualize why a workflow had failed, or can I? I don't understand why this is so difficult :( |
Beta Was this translation helpful? Give feedback.
-
I was trying to achieve the same thing (on success) by passing a service account to the container which is then used to patch the workflow, e.g. something similar to: I can see the message for a few seconds before the workflow goes from I understand that it may be hard to know which message to use, but if I'm setting one myself do you think it would be possible not to have it removed at the end if a value is already set? |
Beta Was this translation helpful? Give feedback.
-
I have workflows which can fail in certain situations, however, there is no point in keeping them around. Analysis of missing data happens later on anyway. Plus, I put entries in a status database and export Prometheus metrics to make it visible.
Is there a way to use an exit handler to ...
secondsAfterFailure
for this particular workflow and set it to0
so that the workflow is being removed sooner?Beta Was this translation helpful? Give feedback.
All reactions