Hello,
I’m working on a bidirectional integration between Appian and an external system via a middleware gateway.
In this setup, we often encounter two categories of errors:
Technical issues
Data issues
My question: What are the best practices for functionally handling these types of errors on the Appian side?
Specifically:
Should we simply display messages to end users via pop-ups or alert banners?
Are there recommended design patterns or built-in Appian features we should consider (such as retry logic, logging strategies, fallback mechanisms, or dynamic UI error messages)?
Any advice for differentiating user-facing errors from those logged for admin troubleshooting?
Thanks in advance for your insights!
Discussion posts and replies are publicly visible
Best Practices for Handling Integration Errors in Appian:
UI Errors: Show user-friendly banners/pop-ups for 4xx errors when integrations are called from interfaces.
Retry Logic: Use exception flows and timers in process models to retry on 5xx errors.
Logging: Log requests/responses for monitoring and admin troubleshooting.
Error Differentiation: Handle 4xx as data issues for users; treat 5xx as technical issues for admins.
for example how we can handle with simple methode this in appian this error comming from another system : Connection Issue: If there is any connection issue between the system in the response message we will send the message "Unable to connect to the remote server" (connection not established and there is no chance of executing API logic so we can not send any error status codes).