We all make mistakes so errors will happen. I would like to be able to set an global error handler microflow that will trigger when unexpected errors occur. Because then from an enduser perspective I can handle this error in a more gracefull way then the red screen the user now is getting.
Regards,
Ronald
Surely it is time to allow logs to be shipped to open telemetry endpoints - really, it isn't hard.
One of the most common things that I have faced is when a user clicks on a button twice and we get the error "Microflow 'XYZ' has not been executed, as it does not allow concurrent execution". Our security is absolutely against showing the user those details, so we had to handle this in each and every Microflow.
If there was an application level exception that we can catch then we can ignore this error or show a friendly message.
so many years and it still not available. Definitely needed
can we also in the console have a way to:
1. select text without the entire screen going to the bottom.
2. show the action where it goes wrong, and be able to go to that action from the console.
3. have smart error handling for common issues such as 'trying to set something to null' trying to parse a value, etc. (this will help new users troubleshoot what is going on)
thx in advance
This would be really useful for us!
Would like to bump this one as it really is needed.
Even just adding an ID to the error message for the end user to then provide to our support team would be ideal.
If 6 years is not considered short term, that's a cause for concern on update cycles for new features...
Any update on this?
User would like to know more about what is happening and to whom to contact exactly
So this will help them more and it will be user friendly.
Anu update on this Andrej? I am sure i am not the only one that would like to be able to :
Any further update on this ? I'm badly looking for a global error handler.
Totally agree. It will improve the user-experience.