- Is it possible to suppress the standard error handling behavior when an external API call fails within a Genesys Cloud Architect flow for our Premium AppFoundry integration?
- The current setup involves a REST Request block calling a third-party service that occasionally returns a 502 Bad Gateway.
- Instead of failing the interaction, the goal is to log the error silently and proceed to the next block without triggering the built-in error handler or dropping the call.
- Testing in the PST timezone environment shows that any non-2xx response forces the flow into the error path immediately.
- The AppFoundry backend handles the retry logic, so the Architect flow should remain agnostic to transient network issues.
- Documentation suggests using a Try/Catch block, but this still requires explicit error handling code rather than a simple bypass.
- Looking for a configuration option or a specific block setting that allows ignoring response codes for non-critical data fetches.
- Current SDK version is 1.200.0, and the integration uses multi-org OAuth tokens for authentication.
- Any insights on achieving this without cluttering the flow with unnecessary error handling blocks would be appreciated.