@Matias.Monday in this post New error handling for integrations! (if others can’t view this, its because its in a private section of the community from when the feature was in preview for marketplace devs.)
You mentioned a 2000 severity code that retries but lets us still supply a message (presumably when it eventually fails after 30 minutes, it would show the error message) however, I cannot find any documentation of this in the documentation related to error handling.
Hello again @anon29275264,
You can send severity code 2000. But it wont let you communicate any message / notification:
We only communicate errors on 4000 severity code and above.
That’s unfortunate, the last error before timeout should return the 2000 notification.
I’m referring to situations like yesterday where errors we can’t control take their toll on things and there is a failure after retries due to the API server being down. Or other API connectivity issues. It would be nice to at least convey to the user what failed. It could just be the runtime error, no notifications themselves for a 2000. But just so it shows in the activity log what failed.
Feature request conversion time?
@anon29275264 done!
