Understanding flow errors
So far, we have seen a happy path and understood how our flow behaves. But even with due diligence and thorough planning and testing, there will always be some scenarios and edge cases that are bound to fail and cause nightmares for your team.
If we do not plan and design our flow, users will run into exceptions with no information on why they failed or some cryptic message that no one can understand. What do they do now? Get frustrated?
To remediate this problem, we need to plan for these exceptions. Issues will happen, and if we are prepared to handle them promptly and fix the root cause, we will create a better user experience.
We can enable this in more than one way:
- By displaying a custom-specific error message and informing the users exactly what caused the issue, they can fix the issue and retry. For example, we can notify the users that certain fields are not accurately populated, or a specific value is invalid.
- For an auto-triggered...
