2 ms·

At the bottom of the thread, there was another company that assumed anything non-successful is a failure (but there was a new success state) which resulted in c

At the bottom of the thread, there was another company that assumed anything non-successful is a failure (but there was a new success state) which resulted in customers retrying and getting charged multiple times It seems the safest option is whenever there is a new API state, a major version bump is needed

mytailorisrich 5y ago
This is still the saner thing to do. There can obviously be 'smart' failures: e.g. Report and block if something unknown is reported to acknowledge the fact that an 'unknown' condition requires to be urgently looked into while preventing further problems. I also find it rather hilarious that the author of the thread then tries to shift the 'blame' to "growth!"...