As a user, I would like to be able to ignore server errors which are transient or outside of my control (e.g. 5XX HTTP response codes, such as the Gateway Timeout (504) errors I received last night) while not ignoring errors which are permanent or may be fixable on my end (e.g. due to missing token, account suspension, etc. - presumably 3XX or 4XX response codes?).
My understanding is that fail-on-error: false will cause the action to succeed after any server error, which could cause fixable errors to be overlooked, and that there is no option or combination of options which would achieve the desired behavior. Is that correct?
Is that a feature you would consider adding? Perhaps by updating fail-on-error to take another value indicating failure should occur for errors which may be fixable by the user (e.g. user, permanent, etc.)?
Thanks for considering,
Kevin
As a user, I would like to be able to ignore server errors which are transient or outside of my control (e.g. 5XX HTTP response codes, such as the Gateway Timeout (504) errors I received last night) while not ignoring errors which are permanent or may be fixable on my end (e.g. due to missing token, account suspension, etc. - presumably 3XX or 4XX response codes?).
My understanding is that
fail-on-error: falsewill cause the action to succeed after any server error, which could cause fixable errors to be overlooked, and that there is no option or combination of options which would achieve the desired behavior. Is that correct?Is that a feature you would consider adding? Perhaps by updating
fail-on-errorto take another value indicating failure should occur for errors which may be fixable by the user (e.g.user,permanent, etc.)?Thanks for considering,
Kevin